Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4009 Add Cfacter 0.4.0 to Windows MSI Change By: Ryan Gard QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4009 Add Cfacter 0.4.0 to Windows MSI Change By: Steve Barlow Scope Change Reason: AIODiscovery Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Ethan Brown commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI Because components.json is currently operating off of origin/master, the AIO MSI has picked up the Windows specific changes necessary to make this run. Josh Cooper has proposed that move the larger discussion around pinning dependencies such as Cfacter to another ticket to further that discussion. /cc Matthaus Owens Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Josh Cooper commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI Release engineering tasks filed as RE-4038 and RE-4039 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Ethan Brown commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI Yes, correct Melissa Stone - thanks for the clarification. The new AIO pipelines are pulling from https://github.com/puppetlabs/puppet-agent/blob/master/configs/components/cfacter.json which specifies origin/master at the moment for the CFacter version. The new pipelines don't use the existing ext/build_defaults.yaml. Such builds were produced successfully yesterday (2/18) for the first time as part of the new pipeline setup: http://builds.puppetlabs.lan/puppet-agent/c012e34025bda8a4df791b93481a79ae3d3b64fe/artifacts/windows/ The big question now is going to be how we pin to a well known CFacter version when we finally ship as I don't believe it's expressed as a pipeline configuration value. This is a question for Matthaus Owens and Justin Stoller Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Justin Stoller commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI IIRC, the idea was that CFacter would be promoted into the puppet-agent build the same was as the Ruby components. I believe last I checked there was some open questions around a compiled project's tests/slave usage would integrate into that workflow and everyone decided that focusing on Puppet was where to put our energy for the time being. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Melissa Stone commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI When building the MSI though the puppet-agent repo (https://github.com/puppetlabs/puppet-agent/blob/master/bin/build-windows.rb), we're likely pulling in cfacter latest from the master branch. I'm not sure if we have that building in an automated fashion yet with jenkins (Matthaus Owens do you know?), but you should be able to test that msi with the latest cfacter code Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Ethan Brown commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI Kylo Ginsberg if you could add the CFacter 0.4.0 release ticket here as a blocker when it's created, that would be super. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Ethan Brown created an issue Puppet / PUP-4009 Add Cfacter 0.4.0 to Windows MSI Issue Type: Task Assignee: Unassigned Components: Windows Created: 2015/02/13 7:47 AM Fix Versions: PUP 4.0.0 Labels: windows Priority: Normal Reporter: Ethan Brown CFacter 0.3.0 is the current version that we're bundling with the MSI. However, this version has a number of issues that prevent it from working properly on Windows, and therefore to be able to use cfacter with external facts (CFACT-219), custom facts, on Windows 2003 (CFACT-166) and inside puppet itself via the --cfacter switch ( CFACT-198 / PUP-3821 / CFACT-208 ), we must ship the fully released CFacter 0.4.0. Note that there were also
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Kylo Ginsberg commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI Ethan Brown I haven't created the ticket yet b/c I expect the cfacter version to be late binding based on how that work proceeds vs puppet-agent 1.0.0 going final (e.g. it might be cfacter 0.4.0 or it might be cfacter 1.0.0). That said, I'm not clear whether lack of a cfacter release is blocking progress for you or not. If you want to tie to a tag rather than a sha in the meantime, we could certainly push a tag and not bother with the other release festivities. (E.g. similar to what we did (or are doing) for hiera 2.0.0-rc1.) If so, let me know. I'm fine pushing a tag. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Ethan Brown commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI Kylo Ginsberg the version we select is actually bound only to a package name that's stored somewhere in build.puppetlabs.lan https://github.com/puppetlabs/puppet/blob/master/ext/build_defaults.yaml#L27-L29 cfacter: archive: x86: 'cfacter-0.3.0-x86.zip' x64: 'cfacter-0.3.0-x64.zip' path: 'http://builds.puppetlabs.lan/cfacter/0.3.0/artifacts/windows' Therefore it is possible + grab 0.3.0 + all patches affecting Windows if we want to pick a known good build number that solves the critical / blocker issues. That said, I think that approach might be a bit confusing if we're doing something different in other environments. I would prefer that we stick to an officially blessed / signed off release. At the very least though, we can't use the current 0.3.0 that we're pinned to based on all the reasons in the description for this ticket (essentially it just doesn't work). /cc Melissa Stone Add Comment
