(QA-2620) update install_pe_client_tools_on to use package repo #26
Conversation
zreichert
changed the title
|
Can one of the admins verify this patch? |
| when /win/ | ||
| package_name = nil | ||
| release_path = "#{opts[:dev_builds_url]}/#{product}/#{ opts[:pe_client_tools_sha] }/artifacts/#{variant}" | ||
| package_name << "_#{opts[:pe_client_tools_version]}-1#{host['platform'].codename}_#{arch}.deb" |
There was a problem hiding this comment.
Don't think we would install a deb package on Windows
| when /windows/ | ||
| when /win/ | ||
| package_name = nil | ||
| release_path = "#{opts[:dev_builds_url]}/#{product}/#{ opts[:pe_client_tools_sha] }/artifacts/#{variant}" |
There was a problem hiding this comment.
variant is not in scope here.
|
Refer to this link for build results (access rights to CI server needed): |
zreichert
force-pushed
the
maint/master/QA-2620_fix_installation_noop_for_nix
branch
from
9ee3bc3 to
b9e7285
Compare
|
Manually validated on Windows2012r2 |
|
Refer to this link for build results (access rights to CI server needed): |
zreichert
force-pushed
the
maint/master/QA-2620_fix_installation_noop_for_nix
branch
from
b9e7285 to
665da12
Compare
|
@johnduarte Updated |
|
Refer to this link for build results (access rights to CI server needed): |
|
Manually validated on Windows2012r2 |
|
Manually validated on OSX 10.11 |
zreichert
changed the title
|
👍 |
|
@nicklewis can you take a look? |
|
retest this please |
|
I haven't tested this out (so there could be typoes / wrong paths, etc), but it makes sense to me. |
|
Refer to this link for build results (access rights to CI server needed): |
|
@puppetlabs/beaker Can I get a review and merge on this? This is blocking CI for a feature intended for Davis. |
|
looks like your last automation run was hitting an intermittent failure. @puppetlabs-jenkins retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
|
@puppetlabs-jenkins retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
|
@puppetlabs-jenkins retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
|
@puppetlabs-jenkins retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
|
@puppetlabs-jenkins retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
|
@puppetlabs-jenkins retest this please This merry-go-round is getting old. How much longer are we going to do this dance? |
|
Refer to this link for build results (access rights to CI server needed): |
|
@puppetlabs-jenkins retest this please |
|
@johnduarte @zreichert this job was temporarily broken as we neglected to update it to use ruby 2.2.5 when we introduced breaking changes into beaker for the 3.0 release. When we updated it to ruby 2.2.5, we ended up breaking it even more, so we had to spend some time debugging that situation and running the validation again. This latest iteration should be good, but, the only certainties in life are death and taxes, so I wouldn't hold your breath. Sorry for pipeline breakage! 🚧 👷 |
|
Refer to this link for build results (access rights to CI server needed): |
|
@puppetlabs-jenkins retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
|
WHHOOOO! |
No description provided.