[JIRA] (JENKINS-36562) Wrong link to JIRA issues from plugin page
Title: Message Title Thomas Fürer resolved as Fixed JENKINS-16997 is already fixed Jenkins / JENKINS-36562 Wrong link to JIRA issues from plugin page Change By: Thomas Fürer Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36758) Thinbackup release 1.7.6 not available in jenkins update center
Title: Message Title Thomas Fürer resolved as Won't Fix ThinBackup with Version 1.8.0 is out now. Jenkins / JENKINS-36758 Thinbackup release 1.7.6 not available in jenkins update center Change By: Thomas Fürer Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-38532) Active Choices Reactive Reference Parameters don't parse equals character ('=') properly.
Title: Message Title Bruno P. Kinoshita started work on JENKINS-38532 Change By: Bruno P. Kinoshita Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Torben Knerr edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Would love to see something like [~johnwynne] proposed here as a an intermediate solution for the current pipeline stage view: https://issues.jenkins-ci.org/browse/JENKINS-33185?focusedCommentId=258129=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-258129 Blue Ocean is a huge update (30 plugins?) and probably not everyone can (or wants) to adopt it and has to stay with the classical jenkins UI for quite a while.Is there any ongoing work in PRs to implement [~johnwynne]'s proposal? Would it even have a chance to be accepted as an intermediate solution? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Torben Knerr commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Would love to see something like John Wynne proposed here as a https://issues.jenkins-ci.org/browse/JENKINS-33185?focusedCommentId=258129=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-258129 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38105) Fail to set reference parameters with different type of drop down list
Title: Message Title Bruno P. Kinoshita resolved as Fixed Jenkins / JENKINS-38105 Fail to set reference parameters with different type of drop down list Change By: Bruno P. Kinoshita Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38105) Fail to set reference parameters with different type of drop down list
Title: Message Title Bruno P. Kinoshita commented on JENKINS-38105 Re: Fail to set reference parameters with different type of drop down list Pull request merged in NodeLabel parameter version 1.7.3. Can you try it again, please, Yang Li? Resolving the issue, but will close after you've confirmed it's gone. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-32680) Review variables expansion in Groovy scripts for active-choices parameters
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Jenkins / JENKINS-32680 Review variables expansion in Groovy scripts for active-choices parameters Change By: Bruno P. Kinoshita Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-32680) Review variables expansion in Groovy scripts for active-choices parameters
Title: Message Title Bruno P. Kinoshita resolved as Fixed Jenkins / JENKINS-32680 Review variables expansion in Groovy scripts for active-choices parameters Change By: Bruno P. Kinoshita Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-32680) Review variables expansion in Groovy scripts for active-choices parameters
Title: Message Title Bruno P. Kinoshita commented on JENKINS-32680 Re: Review variables expansion in Groovy scripts for active-choices parameters I believe this was fixed recently, in the 1.5.x releases. The issue was the way we were collecting the variables. It was being done in part in the abstract class, and other parts in some of the parameter types. It has been fixed to do everything in a single place, with an uniform behavior. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-32965) Issues with active Choice pluggin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-32965 Re: Issues with active Choice pluggin ping Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-31625) Add configuration parameter, which defines, when filter must started work
Title: Message Title
Bruno P. Kinoshita commented on JENKINS-31625
Re: Add configuration parameter, which defines, when filter must started work
Updated the pull request with my last comments, but extremely happy with the code. Kudos Boguslaw Klimas! I created a job with the latest version available in the update center. Then updated the plug-in to the pull request code, and saving the job this is the only change in the config.xml file. {code 'xml'} 27d26 < 1 49d47 < 1
In this case, I had two parameters, a normal active choices, and then a reactive referencing the previous parameter. Everything worked fine. I added a final request for changes regarding the noise in the JS console, and we will have to rethink the text in the documentation later. Ioannis Moutsatsos I read your previous comment now, when I came here to comment in the JIRA ticket. What do you think about this feature? Simply put, it adds a new input box after the check box to enable filter. This option can be any value (we can add validation later, as even negative values are accepted), by default it is set to 1, and the user may set that to 3 (a good value I believe) or even 10, in cases where it is known that parameters will have a common prefix, for example. This will save processing time, and improve the general performance. We may decide to move it (and maybe filter, or other options) under an Advanced section later. Waiting for Ioannis Moutsatsos feedback, and Boguslaw Klimas feedback on the pull request, in order to merge it. Next release in the first or second week of December.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34750) Reactive Parameter updating on click of itself not on change of referenced parameter
Title: Message Title Bruno P. Kinoshita commented on JENKINS-34750 Re: Reactive Parameter updating on click of itself not on change of referenced parameter Andrew Gray Did you have a chance to review Ioannis Moutsatsos's comment? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40052) Office 365 Connector doesn't supply commiter name(s) for events started by SCM change
Title: Message Title Jesse Jacob created an issue Jenkins / JENKINS-40052 Office 365 Connector doesn't supply commiter name(s) for events started by SCM change Issue Type: Improvement Assignee: Srivardhan Hebbar Components: office-365-connector-plugin Created: 2016/Nov/26 5:40 AM Environment: Jenkins 2.33, Windows 2012r2, Java 1.7 64bit, Office 365 Connector 1.3 Labels: scm culprits Priority: Minor Reporter: Jesse Jacob Other plugins like email-ext allow you to list committers/culprits individually in build status messages. I don't know if the connector doesn't provide this level of detail in the webhook message or if my target MS Teams connector is deciding not to render it, so please close the issue if I need to talk to the MS Teams group on their uservoice. Currently the only data I see is "Remarks: Started by an SCM Change". If the build is started by a user action, that users name is listed in the resulting message, but never when it's started by an SCM change. Thanks!
[JIRA] (JENKINS-40051) Office 365 Connector doesn't track UNSTABLE to SUCCESS build status changes with Notify Back To Normal event
Title: Message Title Jesse Jacob created an issue Jenkins / JENKINS-40051 Office 365 Connector doesn't track UNSTABLE to SUCCESS build status changes with Notify Back To Normal event Issue Type: Bug Assignee: Srivardhan Hebbar Components: office-365-connector-plugin Created: 2016/Nov/26 5:35 AM Environment: Jenkins 2.33, Windows 2012r2, Java 1.7 64bit, Office 365 Connector 1.3 Labels: status build-flow Priority: Minor Reporter: Jesse Jacob I'm tempted to call this major because it misses an important use case of Jenkins, which is to understand when problems are corrected. A variety of negative things worth tracking can cause a build status to transition to unstable, which the plugin alerts about just fine, but you also want to know when those negative things are corrected, which this plugin does not do unless you track every success event. Would you consider aligning this plugin more closely with Jenkins status changes in other plugins, e.g. email-ext (https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin)? Email-ext treats the status changes: unstable -> success failure -> success The same way with the "fixed" trigger. I'm not arguing to add another trigger condition to the Office 365 Connector plugin, but just to including UNSTABLE -> SUCCESS status changes to the "Notify Back To Normal" event. Currently only FAILURE -> SUCCESS causes "Notify Back To Normal", which doesn't align well with our use case. When developers generate unstable builds from checking in failing tests or adding code analysis errors, we'd like to know when they've fixed it the same
[JIRA] (JENKINS-40050) JGit fails to find translation bundles
Title: Message Title cowwoc updated an issue Jenkins / JENKINS-40050 JGit fails to find translation bundles Change By: cowwoc Environment: Jenkins 2.33 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40050) JGit fails to find translation bundles
Title: Message Title cowwoc created an issue Jenkins / JENKINS-40050 JGit fails to find translation bundles Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Nov/26 3:12 AM Priority: Minor Reporter: cowwoc I have been using JGit without a problem for a while but all of a sudden my build is failing with the following exception: org.eclipse.jgit.errors.TranslationBundleLoadingException: Loading of translation bundle failed for [org.eclipse.jgit.internal.JGitText, en_US] at org.eclipse.jgit.nls.TranslationBundle.load(TranslationBundle.java:168) at org.eclipse.jgit.nls.GlobalBundleCache.lookupBundle(GlobalBundleCache.java:96) at org.eclipse.jgit.nls.NLS.get(NLS.java:132) at org.eclipse.jgit.nls.NLS.getBundleFor(NLS.java:118) at org.eclipse.jgit.internal.JGitText.get(JGitText.java:59) at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:158) at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:227) at org.eclipse.jgit.revwalk.RevWalk.parseAny(RevWalk.java:859) at org.eclipse.jgit.transport.FetchProcess.askForIsComplete(FetchProcess.java:340) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:160) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1201) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) at org.jenkinsci.plugins.gitclient.JGitAPIImpl$2.execute(JGitAPIImpl.java:606) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50)
[JIRA] (JENKINS-40049) Provide blueocean REST capability for AbstractTestResultAction and AggregatedTestResultAction
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40049 Provide blueocean REST capability for AbstractTestResultAction and AggregatedTestResultAction Issue Type: Task Assignee: James Dumay Components: junit-plugin Created: 2016/Nov/26 3:03 AM Priority: Minor Reporter: James Dumay When a developer subclasses either AbstractTestResultAction and AggregatedTestResultAction in a test reporting plugin (a common pattern) we would like to let the Blue Ocean frontend generalise the display of its data. The Capability annotation is used by plugins to declare it's capability (e.g. that they share a common set of data). This allows the Blue Ocean REST API to let frontend plugins who may be interested in such capability that the action or data can be used through a general contract. Add Comment
[JIRA] (JENKINS-40048) Multiple checkout with pipeline script with nested depot paths causes continous builds
Title: Message Title Nils Carlson commented on JENKINS-40048 Re: Multiple checkout with pipeline script with nested depot paths causes continous builds Paul Allen I have created a pull request for this. As noted, this fixes a very specific issue, not the general case of multiple checkouts in a pipeline (see JENKINS-39652 ) Pull request is here: https://github.com/jenkinsci/p4-plugin/pull/32 This is critical for us as without this patch all our builds trigger on every poll run. :-/ /Nils Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40027) REGRESSION: can't open branches that have / in the name (eg git flow)
Title: Message Title Thorsten Scherler updated JENKINS-40027 Jenkins / JENKINS-40027 REGRESSION: can't open branches that have / in the name (eg git flow) Change By: Thorsten Scherler Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40048) Multiple checkout with pipeline script with nested depot paths causes continous builds
Title: Message Title Nils Carlson created an issue Jenkins / JENKINS-40048 Multiple checkout with pipeline script with nested depot paths causes continous builds Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Nov/25 11:14 PM Environment: Jenkins 2.31 p4-plugin 1.4.10 Priority: Critical Reporter: Nils Carlson When using multiple checkouts, one for the pipeline script and one in the pipeline script where the first is nested inside the second in the depot path, i.e. "///jenkins/Jenkinsfile" in the first checkout and the second is "///...", if the last built change for the first checkout has a lower number than for the second, then continuous builds are triggered. Ideally the p4-plugin should match each checkout with the change for that specific checkout, but this is complicated. Appeasing this exact use-case can be done by setting the last built change to the highest number of the two, ensuring that continuous builds are not triggered for this case. Add Comment
[JIRA] (JENKINS-40048) Multiple checkout with pipeline script with nested depot paths causes continous builds
Title: Message Title Nils Carlson assigned an issue to Nils Carlson Jenkins / JENKINS-40048 Multiple checkout with pipeline script with nested depot paths causes continous builds Change By: Nils Carlson Assignee: Nils Carlson Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-39157) Duplicate Matrix Combination Parameter name on build page
Title: Message Title Julio Gonzalez Gil commented on JENKINS-39157 Re: Duplicate Matrix Combination Parameter name on build page Same problem here with 1.1.0 and Jenkins 2.28 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-39157) Duplicate Matrix Combination Parameter name on build page
Title: Message Title Julio Gonzalez Gil updated an issue Jenkins / JENKINS-39157 Duplicate Matrix Combination Parameter name on build page Change By: Julio Gonzalez Gil Attachment: jenkins.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40047) Add "File ID Parameter" that works just like "Credentials Parameter"
Title: Message Title David Karr created an issue Jenkins / JENKINS-40047 Add "File ID Parameter" that works just like "Credentials Parameter" Issue Type: Improvement Assignee: Dominik Bartholdi Components: config-file-provider-plugin Created: 2016/Nov/25 11:03 PM Priority: Minor Reporter: David Karr It would be better if providing config files to jobs was as clean as providing credentials. When I create a "Credentials Parameter", I only have to specify the stored principal from the credential store. My script uses the parameter as an opaque value. It might be a GUID, but I don't need to know that. Providing managed files to jobs is not as convenient as this. I want to have the ability to add a "File ID Parameter" (can't use "File Parameter", as that already exists). I would just select the particular managed file from a dropdown, and my script would use the value opaquely, just like a credentials parameter. I know I can create a managed file and override the guid value to use a more mnemonic value, but this is still a maintenance issue. Having a hardcoded string in the script to specify the file name is just not optimal. I suppose I could instead provide the id value as a parameter, but that still doesn't eliminate the implicit indirection to the managed file.
[JIRA] (JENKINS-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title Nabil Ghodbane commented on JENKINS-35096 Re: Add support for Jenkins Pipeline to the cppcheck-plugin Hi, Do you know by chance the status of this issue. Can one now invoque Cppcheck in a pipeline and upload the xml output file? thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40045) Support for secret key credentials in Git Plugin
Title: Message Title Mark Waite commented on JENKINS-40045 Re: Support for secret key credentials in Git Plugin The git plugin and git client plugin support username / password credentials (with https protocol URL's) and private key credentials (with ssh and scp protocol URL's). Can you explain in more detail how you envision "secret key credentials" would work? The "Injecting Secrets into Jenkins Builds" describes three techniques to inject credentials into a job. The first, username / password, is supported by the git plugin and git client plugin. The second, "secret file", seems like it would need significantly more definition of how to express the interaction between the contents of the "secret file" and the git program. Are the contents of the secret file intended to be a private key? If so, they why not express that directly as a private key credentials? Are the contents of the secret file intended to be a username / password pair? If so, then why not express that directly using a username / password credential? The third "secret text", seems like it would require defining a convention for the environment variable(s) which would carry the private key or the username / password to the git command. Please clarify how the user of a "secret file" or a "secret text" would use them with the git plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-40046) Add option to disable internal shared library
Title: Message Title
Torsten Reinhard updated an issue
Jenkins / JENKINS-40046
Add option to disable internal shared library
Change By:
Torsten Reinhard
In our Jenkins Setup we are currently using the "internal shared library" (ssh://USERNAME@server:PORT/workflowLibs.git), which is implicit accessible via its "master" Branch.Pipelines using that code are working fine.Now, I´ve *cloned *that repo into a BitBucket Repo for "pretesting" changes with a demo project that resided in a "Folder" inside Jenkins.I´ve configured this folder to use a "shared library" (the cloned one from the internal):Name: cd_workflowlibsDefault version: masterLoad implicitely: trueAllow default version to be overridden: trueThe Url is like: ssh://g...@licdci01.mycompany.net:7999/cd/workflowlibs.gitBranches to build: origin-bitbucket/masterWhen starting my pipeline, the library seems to be loaded correctly: {code} Loading library cd_workflowlibs@master > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin-bitbucket.url ssh://g...@licdci01.mycompany.net:7999/cd/workflowlibs.git # timeout=10Fetching upstream changes from ssh://g...@licdci01.mycompany.net:7999/cd/workflowlibs.git > git --version # timeout=10using GIT_SSH to set credentials SSH Bitbucket Access > git -c core.askpass=true fetch --tags --progress ssh://g...@licdci01.mycompany.net:7999/cd/workflowlibs.git +refs/heads/*:refs/remotes/origin-bitbucket/* > git rev-parse refs/remotes/origin-bitbucket/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin-bitbucket/origin-bitbucket/master^{commit} # timeout=10Checking out Revision 205f22f3563b2c5b224e41fdd8c53d1c22b041d2 (refs/remotes/origin-bitbucket/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 205f22f3563b2c5b224e41fdd8c53d1c22b041d2 {code} The weird thing now is, that new scripts will be executed properly - but changes made to "old", existing scripts aren´t reflected.It seems like the "old" scripts are still being used from the global, internal shared library location (where changes are not yet pushed).After some tests, it came out that there´s an overlapping between scripts:The old version is picked up from the internal repo, the changed version is traced in the console.log - but not used.It would be very helpfull to a) be able to disable the internal repo at allb) extend the output in console.log, which locations are used to find the *.groovy scripts.Currently the console contains only the locations of shared libraries - but no info about the internal repo which may also contains scripts.Thanx for any improvements to make it more clear which script is choosen from which library/repo.TorstenSee also https://groups.google.com/forum/#!searchin/jenkinsci-users/shared$20library%7Csort:relevance/jenkinsci-users/JTACzNkiqEU/nfcbR7fMCQAJ
[JIRA] (JENKINS-40046) Add option to disable internal shared library
Title: Message Title
Torsten Reinhard created an issue
Jenkins / JENKINS-40046
Add option to disable internal shared library
Issue Type:
Improvement
Assignee:
Unassigned
Components:
workflow-cps-global-lib-plugin
Created:
2016/Nov/25 8:42 PM
Environment:
Jenkins 1.653.1 or Jenkins 2.7.21.1-rolling (Enterprise) workflow-cps-global-libs-plugin 2.5
Priority:
Minor
Reporter:
Torsten Reinhard
In our Jenkins Setup we are currently using the "internal shared library" (ssh://USERNAME@server:PORT/workflowLibs.git), which is implicit accessible via its "master" Branch. Pipelines using that code are working fine. Now, I´ve *cloned *that repo into a BitBucket Repo for "pretesting" changes with a demo project that resided in a "Folder" inside Jenkins. I´ve configured this folder to use a "shared library" (the cloned one from the internal): Name: cd_workflowlibs Default version: master Load implicitely: true Allow default version to be overridden: true The Url is like: ssh://g...@licdci01.mycompany.net:7999/cd/workflowlibs.git Branches to build: origin-bitbucket/master When starting my pipeline, the library seems to be loaded correctly: Loading library cd_workflowlibs@master > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin-bitbucket.url ssh://g...@licdci01.mycompany.net:7999/cd/workflowlibs.git # timeout=10 Fetching upstream changes from ssh://g...@licdci01.mycompany.net:7999/cd/workflowlibs.git > git --version # timeout=10 using GIT_SSH to set credentials SSH Bitbucket Access > git -c core.askpass=true fetch --tags --progress ssh://g...@licdci01.mycompany.net:7999/cd/workflowlibs.git +refs/heads/:refs/remotes/origin-bitbucket/ > git rev-parse refs/remotes/origin-bitbucket/master^ {commit} # timeout=10
[JIRA] (JENKINS-40021) Cannot skip admin parameter in job creation
Title: Message Title Goran Sarenkapa updated an issue Jenkins / JENKINS-40021 Cannot skip admin parameter in job creation Change By: Goran Sarenkapa Summary: FeatureCannot Cannot skip admin parameter in job creation Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40018) Support Authorized Domains
Title: Message Title Goran Sarenkapa updated an issue Jenkins / JENKINS-40018 Support Authorized Domains Change By: Goran Sarenkapa Labels: feature-request security zap-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40021) FeatureCannot skip admin parameter in job creation
Title: Message Title Goran Sarenkapa updated an issue Jenkins / JENKINS-40021 FeatureCannot skip admin parameter in job creation Change By: Goran Sarenkapa Labels: bug feature-change zap-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40021) FeatureCannot skip admin parameter in job creation
Title: Message Title Goran Sarenkapa updated an issue Jenkins / JENKINS-40021 FeatureCannot skip admin parameter in job creation Change By: Goran Sarenkapa Summary: Cannot FeatureCannot skip admin parameter in job creation Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40018) Support Authorized Domains
Title: Message Title Goran Sarenkapa updated an issue Jenkins / JENKINS-40018 Support Authorized Domains Change By: Goran Sarenkapa List of authotized domains in admin config in order to restrict the target URL scope. When Zap ZAP on Jenkins is used as a service, the user should not be able to launch a scan against any target and the the target URL should comply to a set of regex rules that would be defined by the administrator in the plugin administration interface. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40018) Support Authorized Domains
Title: Message Title Goran Sarenkapa updated an issue Jenkins / JENKINS-40018 Support Authorized Domains Change By: Goran Sarenkapa Summary: Restrict target URL scope Support Authorized Domains Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40045) Support for secret key credentials in Git Plugin
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-40045 Support for secret key credentials in Git Plugin Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-23685) Bitbucket Plugin to support Pull Request POST hook Management
Title: Message Title Dmitry Erastov edited a comment on JENKINS-23685 Re: Bitbucket Plugin to support Pull Request POST hook Management Is this still the case? It appears to be, because even though I have both pushed changes and created/updated PRs set as webhook triggers in Bitbucket, I only seem to get payloads that relate to pushed commits; nothing that looks like [pull requests payloads ]( | https://confluence.atlassian.com/bitbucket/event-payloads-740262817.html#EventPayloads-Pullrequestevents ) ] . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-23685) Bitbucket Plugin to support Pull Request POST hook Management
Title: Message Title Dmitry Erastov commented on JENKINS-23685 Re: Bitbucket Plugin to support Pull Request POST hook Management Is this still the case? It appears to be, because even though I have both pushed changes and created/updated PRs set as webhook triggers in Bitbucket, I only seem to get payloads that relate to pushed commits; nothing that looks like [pull requests payloads](https://confluence.atlassian.com/bitbucket/event-payloads-740262817.html#EventPayloads-Pullrequestevents). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37462) Polling breaks with multiple slaves with own workspace
Title: Message Title Paul Allen commented on JENKINS-37462 Re: Polling breaks with multiple slaves with own workspace 1.4.10 is now released. It fixes some of the issues around polling and slaves, but there are so many different ways workspaces can be setup and distributed around slaves I can't promise I can cover them all. Poll On Master is no longer required (in fact it has been removed). Polling looks for data on previous builds on the Master before invoking the slaves to run changes on Perforce. In most situations this should be ok, although there are obvious edge conditions on the first build and if a build was aborted or crashed before sync. Please let me know if the fix works for you... and thank you Hugues for the feedback. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-39990) favorite plugin causes Exception at user/name/configure page
Title: Message Title Larry Shatzer, Jr. assigned an issue to James Dumay Jenkins / JENKINS-39990 favorite plugin causes Exception at user/name/configure page Change By: Larry Shatzer, Jr. Assignee: Larry Shatzer, Jr. James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37495) [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout
Title: Message Title Leandro Lucarella commented on JENKINS-37495 Re: [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout Thanks Ethan, this is a nasty regression that prevent a lot of users from upgrading. It would be nice if it can get some attention! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40018) Restrict target URL scope
Title: Message Title Goran Sarenkapa edited a comment on JENKINS-40018 Re: Restrict target URL scope Let me see if i understand correctly. I have my domain, let's call it *mysite.com*and i have three applications under it.* +mysite.com/appA/ index.html +* +mysite.com/appB/ index.html +* +mysite.com/appC/ index.html +In this case, the app under test will be +mysite.com/appA/+ and it will be the Target URL. You want a list in admin configurations that will allow you to restrict the target URL so that if they enter an invalid domain such as +mikesite.com/appA/ index.html + it will fail or return an invalid URL error?Is that correct? In which case, is there really a need this functionality since it's internal usage and provides the same functionality as the UI. Your developers should not be adding external sites to the context either but the tool itself does allow them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40018) Restrict target URL scope
Title: Message Title Goran Sarenkapa edited a comment on JENKINS-40018 Re: Restrict target URL scope Let me see if i understand correctly. I have my domain, let's call it *mysite.com*and i have three applications under it.* +mysite.com/appA/index.html+* +mysite.com/appB/index.html+* +mysite.com/appC/index.html+In this case, the site app under test will be +mysite.com/appA/ index.html + and it will be the Target URL. You want a list in admin configurations that will allow you to restrict the target URL so that if they enter an invalid domain such as +mikesite.com/appA/index.html+ it will fail or return an invalid URL error?Is that correct? In which case, is there really a need this functionality since it's internal usage and provides the same functionality as the UI. Your developers should not be adding external sites to the context either but the tool itself does allow them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40045) Support for secret key credentials in Git Plugin
Title: Message Title Radha Krishna Srimanthula updated an issue Jenkins / JENKINS-40045 Support for secret key credentials in Git Plugin Change By: Radha Krishna Srimanthula Environment: Jenkins 2.33, git-plugin 1.3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40045) Support for secret key credentials in Git Plugin
Title: Message Title Radha Krishna Srimanthula updated an issue Jenkins / JENKINS-40045 Support for secret key credentials in Git Plugin Change By: Radha Krishna Srimanthula Environment: Jenkins 2.33, git-plugin 1. 3 .0.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-33925) Test framework for Jenkinsfile
Title: Message Title Frank Genois commented on JENKINS-33925 Re: Test framework for Jenkinsfile Any updates? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40045) Support for secret key credentials in Git Plugin
Title: Message Title Radha Krishna Srimanthula created an issue Jenkins / JENKINS-40045 Support for secret key credentials in Git Plugin Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2016/Nov/25 6:46 PM Priority: Major Reporter: Radha Krishna Srimanthula Need support for Secret key authentication credentials in Git Plugin Currently, a user is able to create credentials (Secret Key) from within the SCM settings - however, the newly created credentials are not available in the drop down. Add Comment
[JIRA] (JENKINS-40018) Restrict target URL scope
Title: Message Title Goran Sarenkapa edited a comment on JENKINS-40018 Re: Restrict target URL scope Let me see if i understand correctly. I have my domain, let's call it *mysite.com*and i have three applications under it.* +mysite.com/ app*A* appA /index.html+* +mysite.com/ app*B* appB /index.html+* +mysite.com/ app*C* appC /index.html+In this case, the site under test will be +mysite.com/ app*A* appA /index.html+ and it will be the Target URL. You want a list in admin configurations that will allow you to restrict the target URL so that if they enter an invalid domain such as +mikesite.com/ app*A* appA /index.html+ it will fail or return an invalid URL error?Is that correct? In which case, is there really a need this functionality since it's internal usage and provides the same functionality as the UI. Your developers should not be adding external sites to the context either but the tool itself does allow them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40018) Restrict target URL scope
Title: Message Title Goran Sarenkapa commented on JENKINS-40018 Re: Restrict target URL scope Let me see if i understand correctly. I have my domain, let's call it mysite.com and i have three applications under it. mysite.com/app*A*/index.html mysite.com/app*B*/index.html mysite.com/app*C*/index.html In this case, the site under test will be mysite.com/app*A*/index.html and it will be the Target URL. You want a list in admin configurations that will allow you to restrict the target URL so that if they enter an invalid domain such as mikesite.com/app*A*/index.html it will fail or return an invalid URL error? Is that correct? In which case, is there really a need this functionality since it's internal usage and provides the same functionality as the UI. Your developers should not be adding external sites to the context either but the tool itself does allow them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40021) Cannot skip admin parameter in job creation
Title: Message Title Goran Sarenkapa edited a comment on JENKINS-40021 Re: Cannot skip admin parameter in job creation See Let's leave the ticket open, i may consider changing how the functionality works in the future but for now, you can see wiki changes [here|https://wiki.jenkins-ci.org/display/JENKINS/zap-plugin+Jenkins+Settings]. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40021) Cannot skip admin parameter in job creation
Title: Message Title Goran Sarenkapa commented on JENKINS-40021 Re: Cannot skip admin parameter in job creation See changes here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40044) Add support to pass extra --test parameters
Title: Message Title R G created an issue Jenkins / JENKINS-40044 Add support to pass extra --test parameters Issue Type: Improvement Assignee: Andrew Hawker Components: aws-device-farm-plugin Created: 2016/Nov/25 5:26 PM Priority: Minor Reporter: R G Parameters like "appium_wait_for_app_script", "appium_log_level" or "appium_auto_accept_alerts" simply can't be set using the plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37462) Polling breaks with multiple slaves with own workspace
Title: Message Title Hugues Moreau commented on JENKINS-37462 Re: Polling breaks with multiple slaves with own workspace Hi Paul, finally found a moment to install & test the new p4.hpi: success! I can use the much simpler p4sync DSL, and polling seems to behave correctly. Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-38228 Re: Incorrect implementation of `loadUserByUsename`, Users are added on demand If you set configuration parameter "Username Attribute" the user ID always is the same and it is get from this attribute of reply from IdP Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-34612) Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."
Title: Message Title Dragan Bosnjak commented on JENKINS-34612 Re: Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..." Confirming Giovanni Tirloni's findings, being organization admin wasn't enough, after making user an organization owner, webhook was created. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37462) Polling breaks with multiple slaves with own workspace
Title: Message Title Nils Carlson updated an issue Jenkins / JENKINS-37462 Polling breaks with multiple slaves with own workspace Change By: Nils Carlson Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37462) Polling breaks with multiple slaves with own workspace
Title: Message Title Nils Carlson commented on JENKINS-37462 Re: Polling breaks with multiple slaves with own workspace Paul Allen Any chance to get eyes on this issue? Or do you recommend simply not polling multiple workspaces within the same pipeline until this is fixed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40043) Allow custom values for Content-Type Header in Pipelines
Title: Message Title Stephan Burkard created an issue Jenkins / JENKINS-40043 Allow custom values for Content-Type Header in Pipelines Issue Type: Improvement Assignee: Janario Oliveira Components: http-request-plugin Created: 2016/Nov/25 4:06 PM Environment: Jenkins 2.7.3, http-request 1.8.12 Labels: http Priority: Major Reporter: Stephan Burkard When I use the http-request plugin in a pipeline, the page https://jenkins.io/doc/pipeline/steps/http_request/ lists the possible values for the optional headers contentType and acceptType. The fixed list of (very few) types is a killer for the plugin usage, because there is (for example) no value for XML data (text/xml or application/xml). In addition the content-type cannot contain any charset information when it contains only the mime-type. I would like to set a content-type like text/xml; charset=UTF-8 which is currently not possible. When I do not set the contentType parameter, the request arrives at the server with contentType text/plain; charset=ISO-8859-1. Therefore I cannot use the http-request plugin and have to use wget via shell instead. To remove such limitations and increase plugin usage, it would probably be better to allow any string as contentType. There are so many mime-types and charsets available, I don't think this can be limited to an Enumeration.
[JIRA] (JENKINS-23571) Option to control repos cache path directory
Title: Message Title Manuel Ryan commented on JENKINS-23571 Re: Option to control repos cache path directory I have the same need, I manage a lot of jenkins masters and I want the hgcache directory to be outside of $JENKINS_HOME for storage and backup reasons. I have implemented this feature in the following PR : https://github.com/jenkinsci/mercurial-plugin/pull/91 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-27413) Handle file parameters
Title: Message Title Geoffrey Arthaud commented on JENKINS-27413 Re: Handle file parameters Base64 encoding/decoding should do the trick on any master or slave node. Thank you ! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40009) Credentials dropdown empty even after adding a new credential
Title: Message Title Radha Krishna Srimanthula resolved as Not A Defect Not a defect, this feature is not supported yet. Jenkins / JENKINS-40009 Credentials dropdown empty even after adding a new credential Change By: Radha Krishna Srimanthula Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-39824) Plugin does not work with read-only perforce replica
Title: Message Title Karl Wirth commented on JENKINS-39824 Re: Plugin does not work with read-only perforce replica Hi Daniel, A read only replica is a use case we never envisaged because you cannot update the have list during sync. The reason it stopped working in 1.4.9 is that we realized there were a lot of failures the plugin was silently ignoring so invalid builds may have been generated without being flagged to the end users. Therefore the plugin now flags most errors. Can you please confirm that the replica is a read-only and not forwarding replica. Which major version of P4D is this on? Also would it be possible to get a general description of the build that used to work so we can see how you use it. Thanks in advance, Karl Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40009) Credentials dropdown empty even after adding a new credential
Title: Message Title Radha Krishna Srimanthula commented on JENKINS-40009 Re: Credentials dropdown empty even after adding a new credential Thanks for the info Mark! May be this should be a feature request then. Regards, Radha. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40042) Tap Plugin not parsing escape control characters (\033)
Title: Message Title George Adams closed an issue as Fixed Jenkins / JENKINS-40042 Tap Plugin not parsing escape control characters (\033) Change By: George Adams Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40042) Tap Plugin not parsing escape control characters (\033)
Title: Message Title George Adams updated an issue Jenkins / JENKINS-40042 Tap Plugin not parsing escape control characters (\033) Change By: George Adams If I try to parse the following output on Jenkins I get an error message:```TAP version 13ok 1 - commander v2.9.0 --- " # "" \033 " duration_ms: 4439 ...1..1``` Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40014) folder job type not supported by various Plugins and Apps
Title: Message Title Thomas Leufkes commented on JENKINS-40014 Re: folder job type not supported by various Plugins and Apps same problem in the Portlet "Latest Builds with icons" in the Dashboard View Plugin (Hyperlinks of the jobs does not include the folder) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40042) Tap Plugin not parsing escape control characters (\033)
Title: Message Title George Adams created an issue Jenkins / JENKINS-40042 Tap Plugin not parsing escape control characters (\033) Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap-plugin Created: 2016/Nov/25 2:44 PM Environment: Jenkins ver. 2.33, Tap Plugin 2.0.1 Priority: Major Reporter: George Adams Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40036) Dynamic deploy of plugin can fail but Jenkins does not report that
Title: Message Title Oliver Gondža closed an issue as Not A Defect Closing as this is likely not a jenkins problem: https://github.com/jenkinsci/acceptance-test-harness/pull/216#issuecomment-262968837 Jenkins / JENKINS-40036 Dynamic deploy of plugin can fail but Jenkins does not report that Change By: Oliver Gondža Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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,
[JIRA] (JENKINS-38166) Changes link in mail is upper case, but should lower
Title: Message Title Benedikt Brückmann commented on JENKINS-38166 Re: Changes link in mail is upper case, but should lower I suspect the changes for i18n in version 1.18 of the mailer-plugin. I noticed, that the link in my mails ends with /Änderungen: (german localization). So I think it is the MailSender.FailureMail.Changes property from mailer-plugin/src/main/resources/jenkins/plugins/mailer/tasks/i18n/Messages.properties which is appended to the job URL. Ronny Borchert: do you have a colon appended to your link, which wasn't there in older mails? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40030) Big delay before a job is started in TestSuite
Title: Message Title
Pavel Janoušek updated an issue
Jenkins / JENKINS-40030
Big delay before a job is started in TestSuite
Change By:
Pavel Janoušek
I've observed our test cases are running for couple of minutes (approx. around 5-6 minutes) even there are actually only 3 a quite simple tests. I've tried to determine a bottle-neck and (thanks to Oliver) found it is a feature of {{hudson.slaves.NodeProvisioner.NodeProvisionerInvoker}} where is statically defined an initial delay (100sec!) which prolongs every out our test many times. It would be a reasonable time for a production deployment but not for running tests. We need to re-define this value to a low number (let say 1s or even lower). The best place where we should do that is to extend {{ForemanTestRule}} introduced by [PR#27|https://github.com/jenkinsci/foreman-node-sharing-plugin/pull/27].
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-40042) Tap Plugin not parsing escape control characters (\033)
Title: Message Title George Adams updated an issue Jenkins / JENKINS-40042 Tap Plugin not parsing escape control characters (\033) Change By: George Adams If I try to parse the following output on Jenkins I get an error message:```TAP version 13ok 1 - commander v2.9.0 --- "#""\033" duration_ms: 4439 ...1..1``` Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36877) Can't select credentials
Title: Message Title max allan commented on JENKINS-36877 Re: Can't select credentials I'm not quite sure when, but at some point, the problem went away... I have 2 sets of credentials now, only one appears in the plugin. Try adding more credentials and see if they appear!! Maybe there is an off by one error somewhere. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-39601) Improve log
Title: Message Title Ivan Fernandez Calvo resolved as Fixed Jenkins / JENKINS-39601 Improve log Change By: Ivan Fernandez Calvo Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-38228 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40040) Cant restore config.xml
Title: Message Title
Sebastian commented on JENKINS-40040
Re: Cant restore config.xml
This suggestion from https://issues.jenkins-ci.org/browse/JENKINS-27548?focusedCommentId=224827=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-224827 doesn't helped:
System.clearProperty('org.xml.sax.driver')
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-39601) Improve log
Title: Message Title Ivan Fernandez Calvo stopped work on JENKINS-39601 Change By: Ivan Fernandez Calvo Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-39980) Exception error while run Job with HP ALM Quality Center plugin
Title: Message Title Michael Fazio commented on JENKINS-39980 Re: Exception error while run Job with HP ALM Quality Center plugin The plugin is built against V1.565.3 of Jenkins. See "jenkins.version" in https://github.com/S73417H/hp-quality-center-plugin/blob/master/pom.xml#L19. Will need to update the version and then fix any resulting source code incompatibilities with the Jenkins core. It is likely that your Jenkins server is reporting that the version of the plugin is not compatible. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36373) SAML Plugin Disappears when Jenkins is restarted
Title: Message Title Ivan Fernandez Calvo resolved as Cannot Reproduce Jenkins / JENKINS-36373 SAML Plugin Disappears when Jenkins is restarted Change By: Ivan Fernandez Calvo Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-39603) Integrate SAML with LDAP/AD to obtain groups
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-39603 Integrate SAML with LDAP/AD to obtain groups Change By: Ivan Fernandez Calvo Summary: Integrate SAMl SAML with LDAP/AD to obtain groups Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-34867) Jenkins SAML SSO issue
Title: Message Title Ivan Fernandez Calvo resolved as Cannot Reproduce Jenkins / JENKINS-34867 Jenkins SAML SSO issue Change By: Ivan Fernandez Calvo Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40040) Cant restore config.xml
Title: Message Title Sebastian updated an issue Jenkins / JENKINS-40040 Cant restore config.xml Change By: Sebastian Environment: SUSE Linux Enterprise Server 11 (x86_64) Jenkins ver. 1.651.2 (know, quiet old) Job Configuration History Plugin (jobConfigHistory): 2.15Windows Slaves Plugin (windows-slaves): 1.1JUnit Plugin (junit): 1.9Email Extension Plugin (email-ext): 2.40.5Any Build Step Plugin (any-buildstep): 0.1Script Security Plugin (script-security): 1.15FindBugs Plug-in (findbugs): 4.62Translation Assistance plugin (translation): 1.12Mailer Plugin (mailer): 1.16Credentials Plugin (credentials): 1.24SSH Credentials Plugin (ssh-credentials): 1.11Flexible Publish Plugin (flexible-publish): 0.14.1CVS Plug-in (cvs): 2.12Green Balls (greenballs): 1.14Timestamper (timestamper): 1.8.7Copy To Slave Plugin (copy-to-slave): 1.4.4Structs Plugin (structs): 1.5OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.3Run Condition Plugin (run-condition): 1.0LDAP Plugin (ldap): 1.11SonarQube Plugin (sonar): 2.4.4Parameterized Trigger plugin (parameterized-trigger): 2.29Active Directory plugin (active-directory): 1.41Static Analysis Utilities (analysis-core): 1.74Publish Over CIFS (publish-over-cifs): 0.3Subversion Plug-in (subversion): 2.5.3Environment Injector Plugin (envinject): 1.92.1Javadoc Plugin (javadoc): 1.3Hudson global-build-stats plugin (global-build-stats): 1.3Maven Integration plugin (maven-plugin): 2.12.1Ant Plugin (ant): 1.2conditional-buildstep (conditional-buildstep): 1.3.3jQuery plugin (jquery): 1.11.2-0Pipeline: API (workflow-api): 2.6Multijob plugin (jenkins-multijob-plugin): 1.18Workspace Cleanup Plugin (ws-cleanup): 0.32Publish Over SSH (publish-over-ssh): 1.13Resource Disposer Plugin (resource-disposer): 0.3Token Macro Plugin (token-macro): 1.11SCM API Plugin (scm-api): 0.2MapDB API Plugin (mapdb-api): 1.0.6.0External Monitor Job Type Plugin (external-monitor-job): 1.4PAM Authentication plugin (pam-auth): 1.2Matrix Project Plugin (matrix-project): 1.7.1Matrix Authorization Strategy Plugin (matrix-auth): 1.2Pipeline: Step API (workflow-step-api): 2.5Cobertura Plugin (cobertura): 1.9.7Pipeline: Basic Steps (workflow-basic-steps): 2.3SSH Slaves plugin (ssh-slaves): 1.10Reverse Proxy Auth Plugin (reverse-proxy-auth-plugin): 1.0.1 Add Comment
[JIRA] (JENKINS-40040) Cant restore config.xml
Title: Message Title Sebastian updated an issue Jenkins / JENKINS-40040 Cant restore config.xml Change By: Sebastian Environment: SUSE Linux Enterprise Server 11 (x86_64)Jenkins ver. 1.651.2 ( i know, quiet old)Job Configuration History Plugin (jobConfigHistory): 2.15Windows Slaves Plugin (windows-slaves): 1.1JUnit Plugin (junit): 1.9Email Extension Plugin (email-ext): 2.40.5Any Build Step Plugin (any-buildstep): 0.1Script Security Plugin (script-security): 1.15FindBugs Plug-in (findbugs): 4.62Translation Assistance plugin (translation): 1.12Mailer Plugin (mailer): 1.16Credentials Plugin (credentials): 1.24SSH Credentials Plugin (ssh-credentials): 1.11Flexible Publish Plugin (flexible-publish): 0.14.1CVS Plug-in (cvs): 2.12Green Balls (greenballs): 1.14Timestamper (timestamper): 1.8.7Copy To Slave Plugin (copy-to-slave): 1.4.4Structs Plugin (structs): 1.5OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.3Run Condition Plugin (run-condition): 1.0LDAP Plugin (ldap): 1.11SonarQube Plugin (sonar): 2.4.4Parameterized Trigger plugin (parameterized-trigger): 2.29Active Directory plugin (active-directory): 1.41Static Analysis Utilities (analysis-core): 1.74Publish Over CIFS (publish-over-cifs): 0.3Subversion Plug-in (subversion): 2.5.3Environment Injector Plugin (envinject): 1.92.1Javadoc Plugin (javadoc): 1.3Hudson global-build-stats plugin (global-build-stats): 1.3Maven Integration plugin (maven-plugin): 2.12.1Ant Plugin (ant): 1.2conditional-buildstep (conditional-buildstep): 1.3.3jQuery plugin (jquery): 1.11.2-0Pipeline: API (workflow-api): 2.6Multijob plugin (jenkins-multijob-plugin): 1.18Workspace Cleanup Plugin (ws-cleanup): 0.32Publish Over SSH (publish-over-ssh): 1.13Resource Disposer Plugin (resource-disposer): 0.3Token Macro Plugin (token-macro): 1.11SCM API Plugin (scm-api): 0.2MapDB API Plugin (mapdb-api): 1.0.6.0External Monitor Job Type Plugin (external-monitor-job): 1.4PAM Authentication plugin (pam-auth): 1.2Matrix Project Plugin (matrix-project): 1.7.1Matrix Authorization Strategy Plugin (matrix-auth): 1.2Pipeline: Step API (workflow-step-api): 2.5Cobertura Plugin (cobertura): 1.9.7Pipeline: Basic Steps (workflow-basic-steps): 2.3SSH Slaves plugin (ssh-slaves): 1.10Reverse Proxy Auth Plugin (reverse-proxy-auth-plugin): 1.0.1 Add Comment
[JIRA] (JENKINS-40040) Cant restore config.xml
Title: Message Title Sebastian updated an issue Jenkins / JENKINS-40040 Cant restore config.xml Change By: Sebastian Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40040) Cant restore config.xml
Title: Message Title
Sebastian updated an issue
Jenkins / JENKINS-40040
Cant restore config.xml
Change By:
Sebastian
I cant restore a configuration from the history.My workaround is to copy the config.xml to the jobs directory and let the jenkins reload its configuration. { panel code : title=My title java }java.io.IOException: Failed to persist config.xml at hudson.model.AbstractItem.updateByXml(AbstractItem.java:679) at hudson.plugins.jobConfigHistory.JobConfigHistoryProjectAction.doRestore(JobConfigHistoryProjectAction.java:396) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jenkinsci.plugins.reverse_proxy_auth.ReverseProxySecurityRealm$1.doFilter(ReverseProxySecurityRealm.java:92) at
[JIRA] (JENKINS-40041) Filter pipeline by branch (or parameter)
Title: Message Title Tiago Fernandez created an issue Jenkins / JENKINS-40041 Filter pipeline by branch (or parameter) Issue Type: New Feature Assignee: Unassigned Components: build-pipeline-plugin Created: 2016/Nov/25 2:11 PM Priority: Minor Reporter: Tiago Fernandez I would like to have an option where I could filter pipeline view by scm branch name or by any parameter where the user can represent the branch name. You could take as example TeamCity, where build chains (pipeline view) can be filtered by the branch name. We need this, because we are creating template jobs which are branchagnostic, so the branch name can be specified by parameter, so we will have many builds run in the same jobs which will belong to different branches. So we want a way to filter pipeline view so we can see builds for specific branches. Thanks. Add Comment
[JIRA] (JENKINS-40040) Cant restore config.xml
Title: Message Title
Sebastian updated an issue
Jenkins / JENKINS-40040
Cant restore config.xml
Change By:
Sebastian
I cant restore a configuration from the history.My workaround is to copy the config.xml to the jobs directory and let the jenkins reload its configuration. bq. {panel:title=My title} java.io.IOException: Failed to persist config.xml bq. at hudson.model.AbstractItem.updateByXml(AbstractItem.java:679) bq. at hudson.plugins.jobConfigHistory.JobConfigHistoryProjectAction.doRestore(JobConfigHistoryProjectAction.java:396) bq. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) bq. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) bq. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) bq. at java.lang.reflect.Method.invoke(Method.java:606) bq. at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) bq. at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) bq. at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) bq. at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) bq. at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) bq. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) bq. at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) bq. at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) bq. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) bq. at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) bq. at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) bq. at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) bq. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) bq. at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) bq. at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) bq. at org.kohsuke.stapler.Stapler.service(Stapler.java:238) bq. at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) bq. at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) bq. at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) bq. at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) bq. at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) bq. at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) bq. at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) bq. at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) bq. at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) bq. at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86) bq. at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) bq. at
[JIRA] (JENKINS-40040) Cant restore config.xml
Title: Message Title
Sebastian updated an issue
Jenkins / JENKINS-40040
Cant restore config.xml
Change By:
Sebastian
I cant restore a configuration from the history.My workaround is to copy the config.xml to the jobs directory and let the jenkins reload its configuration. {quote} bq. java.io.IOException: Failed to persist config.xml bq. at hudson.model.AbstractItem.updateByXml(AbstractItem.java:679) bq. at hudson.plugins.jobConfigHistory.JobConfigHistoryProjectAction.doRestore(JobConfigHistoryProjectAction.java:396) bq. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) bq. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) bq. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) bq. at java.lang.reflect.Method.invoke(Method.java:606) bq. at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) bq. at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) bq. at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) bq. at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) bq. at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) bq. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) bq. at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) bq. at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) bq. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) bq. at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) bq. at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) bq. at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) bq. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) bq. at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) bq. at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) bq. at org.kohsuke.stapler.Stapler.service(Stapler.java:238) bq. at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) bq. at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) bq. at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) bq. at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) bq. at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) bq. at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) bq. at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) bq. at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) bq. at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) bq. at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86) bq. at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) bq. at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) bq. at
[JIRA] (JENKINS-40040) Cant restore config.xml
Title: Message Title Sebastian created an issue Jenkins / JENKINS-40040 Cant restore config.xml Issue Type: Bug Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2016/Nov/25 2:09 PM Environment: SUSE Linux Enterprise Server 11 (x86_64) Jenkins ver. 1.651.2 Job Configuration History Plugin (jobConfigHistory): 2.15 Windows Slaves Plugin (windows-slaves): 1.1 JUnit Plugin (junit): 1.9 Email Extension Plugin (email-ext): 2.40.5 Any Build Step Plugin (any-buildstep): 0.1 Script Security Plugin (script-security): 1.15 FindBugs Plug-in (findbugs): 4.62 Translation Assistance plugin (translation): 1.12 Mailer Plugin (mailer): 1.16 Credentials Plugin (credentials): 1.24 SSH Credentials Plugin (ssh-credentials): 1.11 Flexible Publish Plugin (flexible-publish): 0.14.1 CVS Plug-in (cvs): 2.12 Green Balls (greenballs): 1.14 Timestamper (timestamper): 1.8.7 Copy To Slave Plugin (copy-to-slave): 1.4.4 Structs Plugin (structs): 1.5 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.3 Run Condition Plugin (run-condition): 1.0 LDAP Plugin (ldap): 1.11 SonarQube Plugin (sonar): 2.4.4 Parameterized Trigger plugin (parameterized-trigger): 2.29 Active Directory plugin (active-directory): 1.41 Static Analysis Utilities (analysis-core): 1.74 Publish Over CIFS (publish-over-cifs): 0.3 Subversion Plug-in (subversion): 2.5.3 Environment Injector Plugin (envinject): 1.92.1 Javadoc Plugin (javadoc): 1.3 Hudson global-build-stats plugin (global-build-stats): 1.3 Maven Integration plugin (maven-plugin): 2.12.1 Ant Plugin (ant): 1.2 conditional-buildstep (conditional-buildstep): 1.3.3 jQuery plugin (jquery): 1.11.2-0 Pipeline: API (workflow-api): 2.6 Multijob plugin (jenkins-multijob-plugin): 1.18 Workspace Cleanup Plugin (ws-cleanup): 0.32 Publish Over SSH (publish-over-ssh): 1.13 Resource Disposer Plugin (resource-disposer): 0.3 Token Macro Plugin (token-macro): 1.11 SCM API Plugin (scm-api): 0.2 MapDB API Plugin (mapdb-api): 1.0.6.0 External Monitor Job Type Plugin (external-monitor-job): 1.4 PAM Authentication plugin (pam-auth): 1.2 Matrix Project Plugin (matrix-project): 1.7.1 Matrix Authorization Strategy Plugin (matrix-auth): 1.2 Pipeline: Step API (workflow-step-api): 2.5 Cobertura Plugin (cobertura): 1.9.7 Pipeline: Basic Steps (workflow-basic-steps): 2.3 SSH Slaves plugin (ssh-slaves): 1.10 Reverse Proxy Auth Plugin (reverse-proxy-auth-plugin): 1.0.1 Priority:
[JIRA] (JENKINS-39503) Bitbucket pull request not approved when "Reset approvals" option is set
Title: Message Title Karol Tyl closed an issue as Won't Fix It occured that this is a bug in Bitbucket - https://bitbucket.org/site/master/issues/13446 Please upvote if it's an issue for you. Jenkins / JENKINS-39503 Bitbucket pull request not approved when "Reset approvals" option is set Change By: Karol Tyl Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-13779) Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM)
Title: Message Title Oliver Gondža reopened an issue Jenkins / JENKINS-13779 Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM) Change By: Oliver Gondža Resolution: Won't Fix Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-13779) Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM)
Title: Message Title Oliver Gondža commented on JENKINS-13779 Re: Git Publisher (tagging) can't work with multipe SCM (ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCM cannot be cast to hudson.plugins.git.GitSCM) Craig Rodrigues, Is there any support for pushing in pipeline? I do not see that on https://jenkins.io/doc/pipeline/steps/ for git or workflow-scm-step. In case users are expected to run that from shell, I do not think this justify as closing reason since used could do that with freestyle as well (multiple SCMs + git push from shell). Consuming credentials from Jenkins is one problem I can see. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-36877) Can't select credentials
Title: Message Title jens persson commented on JENKINS-36877 Re: Can't select credentials I'm having the same issue om a new jenkins instance using the following versions: Jenkins: Version 2.19.3 docker instance Docker: Version 1.11.2 Plugins: Amazon EC2 plugin: Version 1.36 Amazon Web Services SDK: Version 1.11.37 Ant Plugin: Version 1.4 bouncycastle API Plugin: Version 2.16.0 Branch API Plugin: Version 1.11.1 build timeout plugin: Version 1.18 CloudBees Amazon Web Services Credentials Plugin: Version 1.16 Credentials Binding Plugin: Version 1.10 Credentials Plugin: Version 2.1.10 Display URL API: Version 0.5 Durable Task Plugin: Version 1.12 Email Extension Plugin: Version 2.52 External Monitor Job Type Plugin: Version 1.6 Folders Plugin: Version 5.13 Git client plugin: Version 2.1.0 Git plugin: Version 3.0.1 GIT server Plugin: Version 1.7 GitHub API Plugin: Version 1.80 GitHub Branch Source Plugin: Version 1.10 GitHub Organization Folder Plugin: Version 1.5 GitHub plugin: Version 1.23.1 Gradle Plugin: Version 1.25 Icon Shim Plugin: Version 2.0.3 Jackson 2 API Plugin: Version 2.7.3 _javascript_ GUI Lib: ACE Editor bundle plugin: Version 1.1 _javascript_ GUI Lib: Handlebars bundle plugin: Version 1.1.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin: Version 1.2.1 _javascript_ GUI Lib: Moment.js bundle plugin: Version 1.1.1 JUnit Plugin: Version 1.19 LDAP Plugin: Version 1.13 Mailer Plugin: Version 1.18 MapDB API Plugin: Version 1.0.9.0 Matrix Authorization Strategy Plugin: Version 1.4 Matrix Project Plugin: Version 1.7.1 Node Iterator API Plugin: Version 1.5.0 OWASP Markup Formatter Plugin: Version 1.5 PAM Authentication plugin: Version 1.3 Pipeline: Version 2.4 Pipeline Graph Analysis Plugin: Version 1.2 Pipeline: API: Version 2.6 Pipeline: Basic Steps: Version 2.3 Pipeline: Build Step: Version 2.4 Pipeline: Groovy: Version 2.23 Pipeline: Input Step: Version 2.5 Pipeline: Job: Version 2.9 Pipeline: Milestone Step: Version 1.2 Pipeline: Multibranch: Version 2.9.2 Pipeline: Nodes and Processes: Version 2.5 Pipeline: REST API Plugin: Version 2.3 Pipeline: SCM Step: Version 2.3 Pipeline: Shared Groovy Libraries: Version 2.5 Pipeline: Stage Step: Version 2.2 Pipeline: Stage View Plugin: Version 2.3 Pipeline: Step API: Version 2.5 Pipeline: Supporting APIs: Version 2.11 Plain Credentials Plugin: Version 1.3 REPO plugin: Version 1.10.3 Resource Disposer Plugin: Version 0.3 SCM API Plugin: Version 1.3 Script Security Plugin: Version 1.24 SSH Credentials Plugin: Version 1.12 SSH Slaves plugin: Version 1.11 Structs Plugin: Version 1.5 Subversion Plug-in: Version 2.7.1 Timestamper: Version 1.8.7 Token Macro Plugin: Version 2.0 Windows Slaves Plugin: Version 1.2 Workspace Cleanup Plugin: Version 0.32 Add Comment
[JIRA] (JENKINS-39804) Official Blue Ocean docker container
Title: Message Title Yoann Dubreuil commented on JENKINS-39804 Re: Official Blue Ocean docker container I made a proposal in this PR: https://github.com/jenkinsci/blueocean-plugin/pull/628 . The idea would be to schedule the build script like it's already done for the weekly Jenkins image. R. Tyler Croy Would that be ok to run this script on the private CI instance?. If it's preferable, I can spit this up into a new repository only containing the Docker bits. Regarding the demo data, I would like to hand over this repo https://github.com/cloudbees/blueocean-demo-data to jenkinsci. I'll add a Docker compose file to simplify starting the demo. I was also thinking of adding a groovy script which would auto-install BO in the demo data, so people would not need to depend on the BO image but could link the provided volume to any Jenkins image. WDYT? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40039) checkout with commitID does not work in sharedlibaray of pipeline
Title: Message Title
Wen Zhou created an issue
Jenkins / JENKINS-40039
checkout with commitID does not work in sharedlibaray of pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2016/Nov/25 1:42 PM
Labels:
plugin pipeline
Priority:
Minor
Reporter:
Wen Zhou
in the pipeline step: checkout step, use "branches to build" with commitID generated by snippet and it works: node('master'){ stage("1") { checkout changelog: true, poll: true, scm: [$class: 'GitSCM', branches: [[name: 'fc5c534716c171a03eeb31a12c1e0acff700dcbf']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[url: 'ssh://g...@gitlab.is.com:7999/myRepo']]] } } but same code in the shared library does not work: class Git implements Serializable { def checkoutScm() { checkout changelog: true, poll: true, scm: [$class: 'GitSCM', branches: [[name: 'fc5c534716c171a03eeb31a12c1e0acff700dcbf']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[url: 'ssh://g...@gitlab.is.com:7999/myRepo']]] } } } node('master'){ stage("1"){ def git = new Git() git.checkoutScm() Compared with the console, the difference in the later is: Fetching upstream changes from ssh://g...@gitlab.is.com:7999/myRepo.git > /usr/bin/git fetch --tags --progress ssh://g...@gitlab.is.com:7999/myRepo.git +refs/heads/:refs/remotes/origin/ > /usr/bin/git rev-parse refs/remotes/origin/fc5c534716c171a03eeb31a12c1e0acff700dcbf^ {commit} # timeout=10 > /usr/bin/git rev-parse refs/remotes/origin/origin/fc5c534716c171a03eeb31a12c1e0acff700dcbf^{commit} # timeout=10 > /usr/bin/git rev-parse origin/fc5c534716c171a03eeb31a12c1e0acff700dcbf^ {commit} # timeout=10I assume, git rev-parse should done as /usr/bin/git rev-parse
[JIRA] (JENKINS-40023) JGit changelog max limit not working well with merge commits
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-40023 JGit changelog max limit not working well with merge commits Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40009) Credentials dropdown empty even after adding a new credential
Title: Message Title Mark Waite commented on JENKINS-40009 Re: Credentials dropdown empty even after adding a new credential Radha Krishna Srimanthula, the secret text scheme is not "broken". It is not supported by the git plugin. You must use either https protocol with a username / password credential, or a private key with ssh/scp protocol. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40009) Credentials dropdown empty even after adding a new credential
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-40009 Credentials dropdown empty even after adding a new credential Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-39307) pipeline docker execution aborts without reason
Title: Message Title
Wilfried Goesgens commented on JENKINS-39307
Re: pipeline docker execution aborts without reason
Ok, there is a workaround, but man thats hacky! One uses `nohup` to run the script itself, and after that make jenkins poll for the process still existing by examining the existence of its pid via the proc filesystem.
BUILDSCRIPT="nohup ${BUILDSCRIPT} 2>&1 > nohup.out & echo \$! > pid; tail -f nohup.out & wait; kill %2"
try {
if (VERBOSE) {
print(BUILDSCRIPT)
}
sh BUILDSCRIPT
}
catch (err) {
RUNNING_PID=readFile("pid").trim()
def stillRunning=true
while (stillRunning) {
def processStat=""
try{
scripT="cat /proc/${RUNNING_PID}/stat 2>/dev/null"
echo "script: ${scripT}"
processStat = sh(returnStdout: true, script: scripT)
}
catch (x){}
stillRunning=(processStat != "")
sleep 5
}
sh "tail -n 100 nohup.out"
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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
[JIRA] (JENKINS-40038) Parameterized Trigger Plug-in broken with Jenkins core 2.33
Title: Message Title Gary Smith created an issue Jenkins / JENKINS-40038 Parameterized Trigger Plug-in broken with Jenkins core 2.33 Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2016/Nov/25 11:57 AM Environment: Jenkins 2.33 Parameterized Trigger Plugin 2.32 Labels: jenkins plugin Priority: Major Reporter: Gary Smith Parameterized Trigger Plugin 2.32 with "Current build parameters" option was working fine in Jenkins core 2.1. Upgrading to Jenkins core 2.33 caused this plug-in to fail, the parameters were no longer passed on to the downstream job. Add Comment
[JIRA] (JENKINS-40016) Parameterized Trigger Plug-In with "Build on same node" incompatible with Docker Plugin
Title: Message Title Gary Smith updated an issue Jenkins / JENKINS-40016 Parameterized Trigger Plug-In with "Build on same node" incompatible with Docker Plugin Change By: Gary Smith Environment: Jenkins 2. 33 1 Docker Plug-In 0.16.2Parameterized Trigger Plugin 2.32 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
