[JIRA] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Michael Neale commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat I think this will be a lot easier when this is published to the update center BTW Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Michael Neale commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat Ivan Meredith can you share the plugins.txt you used to run this as an image with plugins installed? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Michael Neale commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat Interesting, have run this with jetty/embedded (not just hpi:run) so I expect this may be easy to solve. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plumber-plugin] (JENKINS-35164) What steps are allowed in pipeline action
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-35164
What steps are allowed in pipeline action
Issue Type:
Improvement
Assignee:
Unassigned
Components:
plumber-plugin
Created:
2016/May/27 3:55 AM
Priority:
Major
Reporter:
Michael Neale
When using
pipeline {
..
}
I occasionally hit on odd bugs. Although, as I know it is limited what can be run there, I don't know what is a bug and what isn't. Having some quasi documentation on what can be done with pipeline steps here may help.
Add Comment
[JIRA] [cloudbees-folder-plugin] (JENKINS-34781) Cleanup node workspaces on orphan removal
Title: Message Title Michael Neale assigned an issue to Jesse Glick Jenkins / JENKINS-34781 Cleanup node workspaces on orphan removal Change By: Michael Neale Assignee: Michael Neale Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33839) Pipeline workspace is not browsable via pipeline page
Title: Message Title Michael Neale commented on JENKINS-33839 Re: Pipeline workspace is not browsable via pipeline page The workspace is browseable via a specific build number/run, which then lets you pick a step to find its workspace (eg you click on node, to browse the workspace). You have to know to look at steps however. Perhaps on the build results page there could be a link to "Browse workspace" that explains this (with a link to the steps). Workspace browsing is different by nature in pipeline as Oleg explains, and much more complex to find where things are, perhaps having it "hard to find" is not a bad thing so people don't rely on it. Otherwise, there needs to be a way to roll up all workspaces used and present them in a list. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34321) Browse Workspace is near impossible to find
Title: Message Title Michael Neale closed an issue as Duplicate Jenkins / JENKINS-34321 Browse Workspace is near impossible to find Change By: Michael Neale Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34615) Global error handler for pipeline
Title: Message Title Michael Neale edited a comment on JENKINS-34615 Re: Global error handler for pipeline [~jglick] "Utility library" - I don't know what you mean by that. Is it possible to avoid try/catch/finally ? Can it wrap the whole script to trap those uncaught errors? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34615) Global error handler for pipeline
Title: Message Title Michael Neale commented on JENKINS-34615 Re: Global error handler for pipeline Jesse Glick "Utility library" - I don't know what you mean by that. Is it possible to avoid try/catch/finally ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-34781) Cleanup node workspaces on orphan removal
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-34781 Cleanup node workspaces on orphan removal Change By: Michael Neale Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-34781) Cleanup node workspaces on orphan removal
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-34781 Cleanup node workspaces on orphan removal Issue Type: Improvement Assignee: Michael Neale Components: cloudbees-folder-plugin Created: 2016/May/13 2:16 AM Priority: Major Reporter: Michael Neale With computed folders, such as you may use with multibranch plugins (like github or bitbucket branch source) and a "git flow" way of working, you tend to create a lot of short lived branch jobs. These branch jobs are removed not long after creation (as pull requests are merged) and the job removed, however the workspace on any nodes can live around for up to a month before it is cleaned up by WorkspaceCleanupThread (https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/WorkspaceCleanupThread.java#L115) I am proposing that in the removal of orphans a similar scanning and removal of workspaces could take place. This can supplement the cleanup thread and make for less garbage filling up disk. Add Comment
[JIRA] [github-organization-folder-plugin] (JENKINS-34475) github-org folder is incompatible with git flow implementations - branch names break builds
Title: Message Title Michael Neale commented on JENKINS-34475 Re: github-org folder is incompatible with git flow implementations - branch names break builds I have been bitten by this too, only not with python virtualenv, but "npm run" scripts. Same issue (it seems tripped up by the %). Technically % is reserved: https://en.wikipedia.org/wiki/Filename It is hard to think up an alternative scheme, as people could put anything in branch names right? Note these branch names are used both in uri's in Jenkins as well as file paths: Possibility: feature/TEST-123 > /var/lib/jenkins/jobs/apache-org/jobs/apache-project-aaa-api/branches/feature_ _TEST-123 if it was "special case" for "/" could work, but as other things could appear in branch names, what is the generic encoding to be used for filenames? (as these end up on disk). The rules for branch names: http://stackoverflow.com/questions/3651860/which-characters-are-illegal-within-a-branch-name so some kind of encoding is needed, but perhaps something as generic as URL encoding is overkill, and we can have something that works for both URIs and file systems. As long as it looks reasonable when looking at the URI and also the filesystem that would be nice, but it seems a shame this has to come to this because of poor tooling. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34615) Global error handler for pipeline
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-34615
Global error handler for pipeline
Change By:
Michael Neale
in a pipeline script it is common to catch errors and take action: notifications, gathering test reports of results thus far. This requires a dance around some variants of try/catch or try/finally, sometimes even rethrowing error, setting the currentBuild.result, checking of the currentBuild.result (to see if set previously). Othertimes you tell the test runner to not fail on test failures and set the build result to unstable (which then requires that you use more if/then or throwing exceptions as it will continue on if unstable for the rest of the pipeline script). Would this be better to have a top level event handler? This could clarify the control throw without littering the script with non pipeline related flow controls for the case where there is a failure (and you want to exit but do some things). Likewise for notifications. {noformat} onFailure { ... archive junit results ... notify teams}onSuccess {... notify teams} {noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34615) Global error handler for pipeline
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-34615
Global error handler for pipeline
Change By:
Michael Neale
in a pipeline script it is common to catch errors and take action: notifications, gathering test reports of results thus far. This requires a dance around some variants of try/catch or try/finally, sometimes even rethrowing error, setting the currentBuild.result, checking of the currentBuild.result (to see if set previously). Othertimes you tell the test runner to not fail on test failures and set the build result to unstable (which then requires that you use more if/then or throwing exceptions as it will continue on if unstable for the rest of the pipeline script) . , and then accidentally deploy to production *cough* Would this be better to have a top level event handler? This could clarify the control throw without littering the script with non pipeline related flow controls for the case where there is a failure (and you want to exit but do some things). Likewise for notifications. {noformat}onFailure { ... archive junit results ... notify teams}onSuccess {... notify teams}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34615) Global error handler for pipeline
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-34615
Global error handler for pipeline
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/May/04 10:42 PM
Priority:
Major
Reporter:
Michael Neale
in a pipeline script it is common to catch errors and take action: notifications, gathering test reports of results thus far.
This requires a dance around some variants of try/catch or try/finally, sometimes even rethrowing error, setting the currentBuild.result, checking of the currentBuild.result (to see if set previously). Othertimes you tell the test runner to not fail on test failures and set the build result to unstable (which then requires that you use more if/then or throwing exceptions as it will continue on if unstable for the rest of the pipeline script).
Would this be better to have a top level event handler? This could clarify the control throw without littering the script with non pipeline related flow controls for the case where there is a failure (and you want to exit but do some things). Likewise for notifications.
onFailure { ... archive junit results ... notify teams }
onSuccess { ... notify teams }
[JIRA] [multi-branch-project-plugin] (JENKINS-34522) "Schedule a build" icon for multibranch projects only does a re-index (misleading icon and tooltip)
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-34522 "Schedule a build" icon for multibranch projects only does a re-index (misleading icon and tooltip) Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/May/02 7:09 AM Priority: Minor Reporter: Michael Neale A trap for new users of multibranch project types is that when they are looking at a view, they may see the "schedule a build" icon. It has a tooltip that says "Schedule a build for " - which actually re-indexes the branches. Builds are not guaranteed to result, which may confuse some new users. At least correcting the tooltip would be nice. Add Comment
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Michael Neale commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage I am not sure Philip if those items inside the stages in that deploy pipeline view are parallel or just jobs (steps?) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34321) Browse Workspace is near impossible to find
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-34321 Browse Workspace is near impossible to find Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Apr/19 1:39 AM Priority: Minor Reporter: Michael Neale To browse the workspace when using pipeline, you have to browse to: 1) a specific build number 2) click on pipeline steps 3) find "allocate node : start", click on it 4) click on workspaces on the left. compared to freestyle where the latest workspace available was on the build page. This seems so devilishly hard to find it may as not well be available. Is this right? Add Comment
[JIRA] [github-branch-source-plugin] (JENKINS-34219) Work with github oauth (plugin)
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-34219 Work with github oauth (plugin) Issue Type: Improvement Assignee: Jesse Glick Components: github-branch-source-plugin Created: 2016/Apr/14 4:07 AM Priority: Major Reporter: Michael Neale Github OAuth plugin provides both identify and login a user, and team based authorization if enabled (ie if you are an admin of a team, you are an admin of a job that belongs to that repo). This may make sense in a github branch source world (either to integrate with, or offer a similar oauth feature so users can quickly sign in with github and have credentials configured). Add Comment
[JIRA] [github-branch-source-plugin] (JENKINS-33161) Allow merge commits to be built from origin PRs
Title: Message Title Michael Neale commented on JENKINS-33161 Re: Allow merge commits to be built from origin PRs I think this is becoming more important to bring it to parity with other PR builders people are used to Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-33161) Allow merge commits to be built from origin PRs
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-33161 Allow merge commits to be built from origin PRs Change By: Michael Neale Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-33530) Pull Requests "submitted from origin repository, skipping" not clear why this is skipping
Title: Message Title Michael Neale commented on JENKINS-33530 Re: Pull Requests "submitted from origin repository, skipping" not clear why this is skipping Is this the same thing as https://issues.jenkins-ci.org/browse/JENKINS-33161 ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-34047) Sort github repos in case insensitive fashion
Title: Message Title Michael Neale started work on JENKINS-34047 Change By: Michael Neale Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-34047) Sort github repos in case insensitive fashion
Title: Message Title Michael Neale assigned an issue to Michael Neale Jenkins / JENKINS-34047 Sort github repos in case insensitive fashion Change By: Michael Neale Assignee: Jesse Glick Michael Neale Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-34047) Sort github repos in case insensitive fashion
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-34047 Sort github repos in case insensitive fashion Issue Type: Improvement Assignee: Jesse Glick Components: github-branch-source-plugin Created: 2016/Apr/06 6:25 AM Priority: Minor Reporter: Michael Neale Would be nice to sort without being case sensitive. People with large repo counts (or members of lots of orgs) are rarely consistent with the initial case of their repo names, and this can confuse people into thinking it is unordered. Add Comment
[JIRA] [github-branch-source-plugin] (JENKINS-33768) List of repos should be sorted and/or searchable
Title: Message Title Michael Neale commented on JENKINS-33768 Re: List of repos should be sorted and/or searchable Ah, treeset, nice. Not sure what there ever was to see here... move along. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-33768) List of repos should be sorted and/or searchable
Title: Message Title Michael Neale closed an issue as Not A Defect I am unable to see this NOT ordered, it seems fine, the results are ordered (either a recent change or api change). Searching is fine as per a normal drop down (this was opened on behalf of someone else). nothing to be done! Jenkins / JENKINS-33768 List of repos should be sorted and/or searchable Change By: Michael Neale Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-33161) Allow merge commits to be built from origin PRs
Title: Message Title Michael Neale commented on JENKINS-33161 Re: Allow merge commits to be built from origin PRs If in the happy case of the branch being update with the master when a pull request is opened, ideally a new build would not be triggered, instead it could just use the build previously done on the branch (but it could show up as a new build?? perhaps??). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-33768) List of repos should be sorted and/or searchable
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-33768 List of repos should be sorted and/or searchable Issue Type: Improvement Assignee: Jesse Glick Components: github-branch-source-plugin Created: 2016/Mar/24 12:26 AM Priority: Minor Reporter: Michael Neale When you get a long list of repos for a github org, you get a drop down that is really quite large, but it isn't sorted via name. Ideally it would be sorted and searchable. Add Comment
[JIRA] [workflow-plugin] (JENKINS-27039) Option for input or stage step to cancel older executions
Title: Message Title Michael Neale commented on JENKINS-27039 Re: Option for input or stage step to cancel older executions Feature wise very interesting - but label already has another meaning in Jenkins (and it is a very general world) - is there anything else it could be done? It is great it is block scoped. Milestones being numbered implies an ordinal structure and they are not blocked scoped. If you are making a human lay out the order of something with numbers - doesn't that mean it should be a list of blocks of actions? (I mean, I love basic too, and line numbering.. but...) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27039) Option for input or stage step to cancel older executions
Title: Message Title Michael Neale edited a comment on JENKINS-27039 Re: Option for input or stage step to cancel older executions Feature wise very interesting - but label already has another meaning in Jenkins (and it is a very general world) - is there anything else it could be done called ? It is great it is block scoped. Milestones being numbered implies an ordinal structure and they are not blocked scoped. If you are making a human lay out the order of something with numbers - doesn't that mean it should be a list of blocks of actions? (I mean, I love basic too, and line numbering.. but...) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28119) Link to log of failed step
Title: Message Title Michael Neale commented on JENKINS-28119 Re: Link to log of failed step Maxfield Stewart yes agree. I made https://wiki.jenkins-ci.org/display/JENKINS/Simple+Build+For+Pipeline+Plugin to show how this could be made simpler. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32731) Allow plugins to contribute to Pipeline global library
Title: Message Title Michael Neale commented on JENKINS-32731 Re: Allow plugins to contribute to Pipeline global library Based on what I have seen, I think there is sufficient ability for plugins to add to a global library already - by providing a GlobalVariable extension. Some intelligence needs to be applied around naming and state, but overall, it works just fine (or can be sugared up). There is no need for plugins to "commit" to the workflowLibs repo - I think that would be not right. So I vote we close this in favour of an example/wiki page as "done". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32731) Allow plugins to contribute to Pipeline global library
Title: Message Title
Michael Neale commented on JENKINS-32731
Re: Allow plugins to contribute to Pipeline global library
The only real problem I can forsee is that the names of DSL files in the global lib are, well, global.
eg:
builg.groovy is used as
build { .. }
In the script. If you install 2 plugins that each want to have a build.groovy - how is the conflict resolved? will the second one they install fail? (I fear to suggest qualified imports as that kind of harshes the vibe, but some way to resolve this may be warranted).
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32315) Support FreeBSD in node/npm profiles in plugin parent pom
Title: Message Title Michael Neale commented on JENKINS-32315 Re: Support FreeBSD in node/npm profiles in plugin parent pom For supporting freebsd, I think that we should fall back to using pre-installed node if a binary for the platform is not able to be found. In the build output it can say "WARNING using XYZ as unable to install exact version required by this plugin", or perhaps compare the system version with the required version for compatibility. The result being it is the builders responsibility to ensure a compatible version is available on $PATH Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32315) Support FreeBSD in node/npm profiles in plugin parent pom
Title: Message Title Michael Neale commented on JENKINS-32315 Re: Support FreeBSD in node/npm profiles in plugin parent pom Tom FENNELLY do you mean --quiet ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-31717) docker-build-publish plugin no longer works with spaces in the workspace path
Title: Message Title Michael Neale commented on JENKINS-31717 Re: docker-build-publish plugin no longer works with spaces in the workspace path Carlos Sanchez looks like this was caused by this merge: https://github.com/jenkinsci/docker-build-publish-plugin/commit/73c8a2b0f2838df38b46e9b50f47b0133ffde35c#diff-a7c45f7e2ba80619b5aad549aadc5ef3R322 ie: https://github.com/jenkinsci/docker-build-publish-plugin/blob/master/src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java#L323 which won't work if the workspace has space in its name (probably common). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-31717) docker-build-publish plugin no longer works with spaces in the workspace path
Title: Message Title Michael Neale commented on JENKINS-31717 Re: docker-build-publish plugin no longer works with spaces in the workspace path Matthew Baggett so a path with no spaces is ok? this does seem like a regression. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [codedeploy-plugin] (JENKINS-31332) CodeDeploy Plugin revision date time pattern
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-31332 CodeDeploy Plugin revision date time pattern Change By: Michael Neale Component/s: amazon-ecs-plugin Component/s: deploy-plugin Component/s: jenkinslint-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [codedeploy-plugin] (JENKINS-31331) CodeDeploy Plugin bucket region error
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-31331 CodeDeploy Plugin bucket region error Change By: Michael Neale Component/s: plugin-usage-plugin Component/s: jenkinslint-plugin Component/s: amazon-ecs-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [amazon-ecs-plugin] (JENKINS-31331) CodeDeploy Plugin bucket region error
Title: Message Title Michael Neale commented on JENKINS-31331 Re: CodeDeploy Plugin bucket region error Nicolas De Loof is this deliberately assigned to you or was it an auto assign based on component selection? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [amazon-ecs-plugin] (JENKINS-31332) CodeDeploy Plugin revision date time pattern
Title: Message Title Michael Neale commented on JENKINS-31332 Re: CodeDeploy Plugin revision date time pattern Nicolas De Loof is this deliberately assigned to you or was it an auto assign based on component selection? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28119) Link to log of failed step
Title: Message Title Michael Neale commented on JENKINS-28119 Re: Link to log of failed step Given a common use for this will be to slap a try/catch around everything to get failure messages, would it be possible to have a: onFailure DSL that effectively does the same thing? (not sure if this is possible in the current form of things). Ideally this could be scoped to stage, but that may be just too much to ask. The ideal is to make it not too much more work than what people experience now with freestyle, in WF terms. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28119) Link to log of failed step
Title: Message Title Michael Neale commented on JENKINS-28119 Re: Link to log of failed step In a freestyle job the config is still simpler than the proposed above, having a global "catch all" that sends failure (with pertinent details) would be nice to bring it up to parity. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions
Title: Message Title Michael Neale commented on JENKINS-24338 Re: Issues with docker permissions @jdmulloy - the one for the docker build publish plugin. — NOTE Following notes appear to be missing due to data loss from issue tracker (from joseph): With Docker 1.7.1 on CentOS 7 I had to edit the SocketGroup setting in /usr/lib/systemd/system/docker.socket [Unit] Description=Docker Socket for the API PartOf=docker.service [Socket] ListenStream=/var/run/docker.sock SocketMode=0660 SocketUser=root SocketGroup=jenkins [Install] WantedBy=sockets.target Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-token-root-plugin] (JENKINS-29515) Github oauth breaks "Trigger builds remotely"
Title: Message Title Michael Neale commented on JENKINS-29515 Re: Github oauth breaks "Trigger builds remotely" Thanks Sam. I think there is a structural change that can probably be made to github oauth plugin to allow the root token to work at least. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title Michael Neale commented on JENKINS-25791 Re: User.impersonate throws ClassCastException when using GitHub auth Yes this still seems to be a problem. A duplicate ticket was opened here: https://issues.jenkins-ci.org/browse/JENKINS-29515 I know build root token works with some other identity plugins (such as openid) so perhaps there is a way to make github oauth work that way as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-token-root-plugin] (JENKINS-29515) Github oauth breaks "Trigger builds remotely"
Title: Message Title Michael Neale commented on JENKINS-29515 Re: Github oauth breaks "Trigger builds remotely" Sam I recommend closing this and pointing to the newrely reopened: https://issues.jenkins-ci.org/browse/JENKINS-25791 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-token-root-plugin] (JENKINS-29515) Github oauth breaks "Trigger builds remotely"
Title: Message Title Michael Neale edited a comment on JENKINS-29515 Re: Github oauth breaks "Trigger builds remotely" Yes I was going to suggest that the token root plugin would solve this - but it appears Sam has already tried it. I know build root token plugin has worked for other identity providers. Based on: https://issues.jenkins-ci.org/browse/JENKINS-25791 - it looks like it is not related to PR#37 - but do you want to try an older version to check? It can't hurt. Maybe some special case code is needed for this. I don't think people come across this a lot as they tend to either a) use a github oauth token to interact with jenkins or b) use github to trigger builds directly. If we can confirm it isn't a recent breakage perhaps should close this as a dupe of #25791 and move discussion over to there? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-token-root-plugin] (JENKINS-29515) Github oauth breaks "Trigger builds remotely"
Title: Message Title Michael Neale commented on JENKINS-29515 Re: Github oauth breaks "Trigger builds remotely" Yes I was going to suggest that the token root plugin would solve this - but it appears Sam has already tried it. I know build root token plugin has worked for other identity providers. Based on: https://issues.jenkins-ci.org/browse/JENKINS-25791 - it looks like it is not related to PR#37 - but do you want to try an older version to check? It can't hurt. Maybe some special case code is needed for this. I don't think people come across this a lot as they tend to either a) use a github oauth token to interact with jenkins or b) use github to trigger builds directly. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions
Title: Message Title Michael Neale commented on JENKINS-24338 Re: Issues with docker permissions Joseph - interesting. Perhaps that is worth a PR to the readme as systemd setups like that are probably becoming pretty common - and locking down the socket is the right thing to do? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-28931) Docker build & publish plugin sets the image name twice
Title: Message Title Michael Neale commented on JENKINS-28931 Re: Docker build & publish plugin sets the image name twice agree should be a badge (lobbed this at carlos as I won't have a chance to look at it). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-28931) Docker build & publish plugin sets the image name twice
Title: Message Title Michael Neale assigned an issue to Carlos Sanchez Jenkins / JENKINS-28931 Docker build & publish plugin sets the image name twice Change By: Michael Neale Assignee: Michael Neale Carlos Sanchez Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-28618) docker image pushed on build failure
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-28618 docker image pushed on build failure Change By: Michael Neale Assignee: Michael Neale Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-28600) Support using a non-default Dockerfile
Title: Message Title Michael Neale assigned an issue to Carlos Sanchez Jenkins / JENKINS-28600 Support using a non-default Dockerfile Change By: Michael Neale Assignee: Michael Neale Carlos Sanchez Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-28677) Use Docker tool Installations from Docker commons
Title: Message Title Michael Neale assigned an issue to Carlos Sanchez Jenkins / JENKINS-28677 Use Docker tool Installations from Docker commons Change By: Michael Neale Assignee: Michael Neale Carlos Sanchez Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-28770) Support for promoted build plugin to promote images
Title: Message Title Michael Neale assigned an issue to Carlos Sanchez Jenkins / JENKINS-28770 Support for promoted build plugin to promote images Change By: Michael Neale Assignee: Michael Neale Carlos Sanchez Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-28802) Attempts to tag with "c" cause "Multiple IDs found with provided prefix"
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-28802 Attempts to tag with "c" cause "Multiple IDs found with provided prefix" Change By: Michael Neale Assignee: Michael Neale Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error "Please login prior to push" after publishing the image
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-27229 Docker publish plugin throws error "Please login prior to push" after publishing the image Change By: Michael Neale Assignee: Michael Neale Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27851) Failure of docker build command does not fail build step
Michael Neale resolved JENKINS-27851 as Duplicate Failure of docker build command does not fail build step Duplicate of JENKINS-27970 Change By: Michael Neale (20/Apr/15 5:33 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-25690) Pull base docker image to make sure it's up to date
Michael Neale resolved JENKINS-25690 as Fixed Pull base docker image to make sure it's up to date Change By: Michael Neale (23/Mar/15 10:25 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-25690) Pull base docker image to make sure it's up to date
Michael Neale commented on JENKINS-25690 Pull base docker image to make sure it's up to date Thanks Jo - put some comments on the PR. Looks good, and thanks for this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27164) docker-build-publish-plugin broken compatibility with token-macro-plugin
Michael Neale resolved JENKINS-27164 as Fixed docker-build-publish-plugin broken compatibility with token-macro-plugin Fixed in 0.12 which should be in a maven repo near you shortly. Thanks for spotting this and also diagnosing what was the cause - made the fix easy. Change By: Michael Neale (13/Mar/15 7:43 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27164) docker-build-publish-plugin broken compatibility with token-macro-plugin
Michael Neale commented on JENKINS-27164 docker-build-publish-plugin broken compatibility with token-macro-plugin yes it could be the order in which the macros are expanded, which means it should be easy to fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error "Please login prior to push" after publishing the image
Michael Neale resolved JENKINS-27229 as Cannot Reproduce Docker publish plugin throws error "Please login prior to push" after publishing the image Change By: Michael Neale (12/Mar/15 12:49 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error "Please login prior to push" after publishing the image
Michael Neale commented on JENKINS-27229 Docker publish plugin throws error "Please login prior to push" after publishing the image I can't reproduce this. I cleared my ~/.dockercfg and then put in my details into jenkins- and it logged in and worked. I would suggest removing the ~/.dockercfg - and then trying again. Also - check you can push from the same machine as the same user with docker login being called. Otherwise - it is something odd with the registry config. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error "Please login prior to push" after publishing the image
Michael Neale commented on JENKINS-27229 Docker publish plugin throws error "Please login prior to push" after publishing the image can you share more of your config for the job and plugin? that looks lik eit is missing the username in the settings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions
Michael Neale resolved JENKINS-24338 as Won't Fix Issues with docker permissions Closing this as work-around seems the "correct" thing to do. Change By: Michael Neale (25/Feb/15 8:47 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-25689) Multiple tagging of docker images
Michael Neale resolved JENKINS-25689 as Fixed Multiple tagging of docker images This was addressed by a few recent pull requests and other improvements. Change By: Michael Neale (25/Feb/15 8:48 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27132) Build not properly inheriting environment
Michael Neale commented on JENKINS-27132 Build not properly inheriting environment Not sure what you mean by environment variables - in a docker build - it can't really be parametrised by environment variables (the idea is that it runs the same, the Dockerfile is self describing). Can you explain more the steps you are doing? The environment from jenkins is provided the same as for a freestyle step when running the docker command - but that won't mean anything when running a docker build. I am probably not understanding what you are doing exactly - I gather in your image somewhere are pre-compiled assets you need to publish? what does it look like when you script it from outside? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish] (JENKINS-24338) Issues with docker permissions
Michael Neale commented on JENKINS-24338 Issues with docker permissions Can you try docker command in a regular freestyle job? Also - you can have the docker client for the jenkins user logged in outside of jenkins too (then jenkins doesn't need to care about logging in for you - is that what you were trying to do anyway?) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24261) Assembla browser breaks config page
Michael Neale commented on JENKINS-24261 Assembla browser breaks config page Thanks Mark - yes I assumed it was tiny mistake. Given enough users we see all bugs like that if it is likely to happen again - could a reflection based test look for the occurrence of appropriately named resources along with the classes? (if it is unlikely to happen again, don't bother). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24261) Assembla browser breaks config page
Michael Neale created JENKINS-24261 Assembla browser breaks config page Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 14/Aug/14 4:12 AM Description: It seems that some commits or files were missing from the 2.2.4 release plugin, https://github.com/jenkinsci/git-plugin/tree/git-2.2.4/src/main/resources/hudson/plugins/git/browser is missing Assembla - but it is a valid browser. This is fixed in master: https://github.com/jenkinsci/git-plugin/tree/master/src/main/resources/hudson/plugins/git/browser/AssemblaWeb but I thought it was important enough to warrant a bug. b/hudson/listScmBrowsers.jelly:42:77: No page found 'config.jelly' for class hudson.plugins.g it.browser.AssemblaWeb$ASSEMBLAWEBDescriptor ... 2014-08-14_02:08:37.95675 org.apache.commons.jelly.JellyTagException: jar:file:/opt/jenkins/jenkins-wars/a b8ce365aaaefd7ce743bba511a7441850f7fd8329aafe9e2cf106a702ccb948/WEB-INF/lib/jenkins-core-1.554.2.3.jar!/li b/hudson/listScmBrowsers.jelly:42:77: No page found 'config.jelly' for class hudson.plugins.g it.browser.AssemblaWeb$ASSEMBLAWEBDescriptor Project: Jenkins Priority: Major Reporter: Michael Neale This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24261) Assembla browser breaks config page
Michael Neale updated JENKINS-24261 Assembla browser breaks config page Change By: Michael Neale (14/Aug/14 4:17 AM) Description: It seems that some commits or files were missing from the 2.2.4 release plugin, https://github.com/jenkinsci/git-plugin/tree/git-2.2.4/src/main/resources/hudson/plugins/git/browseris missing Assembla - but it is a valid browser. This is fixed in master:https://github.com/jenkinsci/git-plugin/tree/master/src/main/resources/hudson/plugins/git/browser/AssemblaWebbut I thought it was important enough to warrant a bug. b/hudson/listScmBrowsers.jelly:42:77: No page found 'config.jelly' for class hudson.plugins.g it.browser.AssemblaWeb$ASSEMBLAWEBDescriptor... 2014-08-14_02:08:37.95675 org.apache.commons.jelly.JellyTagException: jar:file:/opt/jenkins/jenkins-wars/a b8ce365aaaefd7ce743bba511a7441850f7fd8329aafe9e2cf106a702ccb948 .. /WEB-INF/lib/jenkins-core -1 . 554 . 2.3.jar! /li b/hudson/listScmBrowsers.jelly:42:77: No page found 'config.jelly' for class hudson.plugins.g it.browser.AssemblaWeb$ASSEMBLAWEBDescriptor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish] (JENKINS-24045) Allow multiple repository login
Michael Neale commented on JENKINS-24045 Allow multiple repository login Never mind It will happen at some point. FYI as this uses the docker command line - it is possible that if you pre-login to all the registries - you won't need to tell jenkins about it - it will use the underlying systems credentials when pushing (and pulling). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish] (JENKINS-24045) Allow multiple repository login
Michael Neale commented on JENKINS-24045 Allow multiple repository login Nicolas I agree. I am hoping to get time to work on an enhancement that uses the Credentials plugin - this means that multiple credentials can be stored centrally - and then you can pick one per job. emails/username/password and server can be stored as part of the named credential - then on each job you could pick from a drop down (perhaps with a default?) which credential (and thus which registry) to use. I am just a bit lost on how to implement things with credentials (custom ones) so have asked for help. If you know anything or want to have a crack - by all means please do! (not critical for me either but moving to the credentials plugin I think is pretty important - so why not allow multiple registries per step- think of it like git - you can pick credential at the time you put in in your repo). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish] (JENKINS-24045) Allow multiple repository login
Michael Neale resolved JENKINS-24045 as Fixed Allow multiple repository login Fixed - on its way to update center. Change By: Michael Neale (31/Jul/14 7:03 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23646) Build tokens should be replaced by build token root plugin
Michael Neale edited a comment on JENKINS-23646 Build tokens should be replaced by build token root plugin A failing permission check showing a warning could be acceptable - as it could suggest the 2 solutions (add built root token or allow anon read access). Even the text of it changing to emphasise that it won't work on secured jenkins (by default) with suggestions would also be good. A variation of the 1st one if to just include the build toot token action in core https://github.com/jenkinsci/build-token-root-plugin/blob/master/src/main/java/org/jenkinsci/plugins/build_token_root/BuildRootAction.java - a 100 odd lines - vs having it as an optional plugin (users can then be encouraged to use that url if they need access from outside). I would prefer the latter as a permission check doesn't have to be performed - we can just direct people to use the parametrised root path. Everything existing would work as is. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23646) Build tokens should be replaced by build token root plugin
Michael Neale commented on JENKINS-23646 Build tokens should be replaced by build token root plugin A failing permission check showing a warning could be acceptable - as it could suggest the 2 solutions (add built root token or allow anon read access). Even the text of it changing to emphasise that it won't work on secured jenkins (by default) with suggestions would also be good. A variation of the 1st one if to just include the build toot token action in core https://github.com/jenkinsci/build-token-root-plugin/blob/master/src/main/java/org/jenkinsci/plugins/build_token_root/BuildRootAction.java - a 100 odd lines - vs having it as an optional plugin (users can then be encouraged to use that url if they need access from outside). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23646) Build tokens should be replaced by build token root plugin
Michael Neale commented on JENKINS-23646 Build tokens should be replaced by build token root plugin OK some options: 1) Include root token plugin with core - and update the docs to suggest using the root path by default. This ensures that it will work as expected, and current things work 2) Modify the build token feature to detect that global security is applied - it is no longer visible. The user will need to install the root token plugin to make the feature work again. both maintain compatibility, and get it out of the current broken state. #1 is bundling (mostly, and a doc change), #2 maybe slightly harder than meets the eye. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23646) Build tokens should be replaced by build token root plugin
Michael Neale edited a comment on JENKINS-23646 Build tokens should be replaced by build token root plugin OK some options: 1) Include root token plugin with core - and update the docs to suggest using the root path by default. This ensures that it will work as expected, and current things work 2) Modify the build token feature to detect that global security is applied and if it is, it won't show the checkbox for the build token at all (as there is no point, it will never ever work). The user will need to install the root token plugin to allow token triggered builds. both maintain compatibility, and get it out of the current broken state. #1 is bundling (mostly, and a doc change), #2 maybe slightly harder than meets the eye. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-token-root] (JENKINS-23646) Build token plugin should be replaced by build token root plugin
Michael Neale created JENKINS-23646 Build token plugin should be replaced by build token root plugin Issue Type: Bug Assignee: Jesse Glick Components: build-token-root Created: 02/Jul/14 1:40 AM Description: As it stands - the build token plugin is not useful in any realistic scenario. As soon as you put any sort of security over jenkins - it will not work and build token-root plugin will be needed. Why not depracate build token plugin, and make build token root the only replacement. Environment: Any Project: Jenkins Priority: Major Reporter: Michael Neale This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
