[JIRA] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes
Title: Message Title Thomas Maslen commented on JENKINS-25241 Re: svn+ssh checkout fails on remote nodes I encountered this with the current (2.5.7) version of the Subversion plugin running on Jenkins 1.598 (yup, serves me right for running a version that old). The root cause was JENKINS-27289 , so upgrading to a jenkins.war that fixes JENKINS-27289 made svn+ssh work properly on slaves: 1.618 and above have the ideal version of the MaskingClassLoader fix 1.614 and above have a good-enough version of the fix 1.609.2 and 1.609.3 have the good-enough version of the fix (and still support JDK 1.6) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat edited a comment on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring Here are the libs in your plugins in the attached text file [^libs_in_those_plugins.txt], ignoring your plugins versions.There are 2 of your plugins including log4j: violations.hpi and testflight.hpi (both are including log4j v1.2.9).I am not totally convinced that one of those 2 plugins are the cause of the issue, so to find the cause I suggest to try:- install a new version of the monitoring plugin, after removing /WEB-INF/lib/slf4j-api-1.6.3.jar from the hpi file. (I am not convinced that it will fix the issue either, but who knows ? slf4j is not really needed in the plugin anyway.)- uninstall violations.hpi and testflight.hpi- say here what is your servlet container. Is it the default winstone/jetty or tomcat or jboss ?- do you have some log4j file directly in your server container ? (tomcat/lib/ for example)- otherwise I don't know, except that you have many many plugins (107 in fact) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat edited a comment on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring Here are the libs in your plugins in the attached [^libs_in_those_plugins. txt file ] , ignoring your plugins versions.There are 2 of your plugins including log4j: violations.hpi and testflight.hpi (both are including log4j v1.2.9).I am not totally convinced that one of those 2 plugins are the cause of the issue, so to find the cause I suggest to try:- install a new version of the monitoring plugin, after removing /WEB-INF/lib/slf4j-api-1.6.3.jar from the hpi file. (I am not convinced that it will fix the issue either, but who knows ? slf4j is not really needed in the plugin anyway.)- uninstall violations.hpi and testflight.hpi- say here what is your servlet container. Is it the default winstone/jetty or tomcat or jboss ?- do you have some log4j file directly in your server container ? (tomcat/lib/ for example)- otherwise I don't know, except that you have many many plugins (107 in fact) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title James Dumay edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage I am asking for feedback so we can move forward on this issueTables make a lot of sense when you want scanability and comparison between each row (for example, comparing duration, which seems to be a key feature of the stage view). Adding parallel steps in a "cell" will destroy that scanability and start making the view negatively information dense.We've been thinking of representing single pipeline results like the screenshot below. Timings would either be a detail on hover or shown on a seperate graph (graphs are way better at visualising time comparisons). For each run of the pipeline we would show something like:!pipeline.png!Example of stage duration comparison graph : . X=Pipeline runs going forward in time and Y=duration of each stage !stage-duration.png! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title James Dumay edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage I am asking for feedback so we can move forward on this issueTables make a lot of sense when you want scalability scanability and easy comparison between each row (for example, comparing duration, which seems to be a key feature of the stage view). Adding parallel steps in a "cell" will destroy that scalability scanability and start making it the view negatively information dense.We've been thinking of representing single pipeline results like the screenshot below. Timings would either be a detail on hover or shown on a seperate graph (graphs are way better at visualising time comparisons). For each run of the pipeline we would show something like:!pipeline.png!Example of stage duration comparison graph:!stage-duration.png! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title James Dumay edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage I am asking for feedback so we can move forward on this issue Tables make a lot of sense when you want scalability and easy comparison between each row (for example, comparing duration, which seems to be a key feature of the stage view). Adding parallel steps in a "cell" will destroy that scalability and start making it negatively information dense.We've been thinking of representing single pipeline results like the screenshot below. Timings would either be a detail on hover or shown on a seperate graph (graphs are way better at visualising time comparisons). For each run of the pipeline we would show something like:!pipeline.png |thumbnail !Example of stage duration comparison graph:!stage-duration.png |thumbnail ! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-33185 Visualize parallel steps within a Pipeline Stage Tables make a lot of sense when you want scalability and easy comparison between each row (for example, comparing duration, which seems to be a key feature of the stage view). Adding parallel steps in a "cell" will destroy that scalability and start making it negatively information dense. We've been thinking of representing single pipeline results like the screenshot below. Timings would either be a detail on hover or shown on a seperate graph (graphs are way better at visualising time comparisons). For each run of the pipeline we would show something like: Example of stage duration comparison graph: Change By: James Dumay Attachment: stage-duration.png Attachment: pipeline.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat updated an issue Jenkins / JENKINS-32441 SEVERE: Failed Loading plugin monitoring Here are the libs in your plugins in the attached txt file, ignoring your plugins versions. There are 2 of your plugins including log4j: violations.hpi and testflight.hpi (both are including log4j v1.2.9). I am not totally convinced that one of those 2 plugins are the cause of the issue, so to find the cause I suggest to try: install a new version of the monitoring plugin, after removing /WEB-INF/lib/slf4j-api-1.6.3.jar from the hpi file. (I am not convinced that it will fix the issue either, but who knows ? slf4j is not really needed in the plugin anyway.) uninstall violations.hpi and testflight.hpi say here what is your servlet container. Is it the default winstone/jetty or tomcat or jboss ? do you have some log4j file directly in your server container ? (tomcat/lib/ for example) otherwise I don't know, except that you have many many plugins (107 in fact) Change By: evernat Attachment: libs_in_those_plugins.txt Add Comment
[JIRA] [warnings-plugin] (JENKINS-32150) Cannot resolve relative filenames referencing parent directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32150 Re: Cannot resolve relative filenames referencing parent directory Code changed in jenkins User: Ulli Hafner Path: src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_core/AnalysisAction.java src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_core/AnalysisSettings.java src/test/java/plugins/WarningsPluginTest.java src/test/resources/warnings_plugin/jenkins-32150/compile-log.txt src/test/resources/warnings_plugin/jenkins-32150/directory-a/file-in-subdir.txt src/test/resources/warnings_plugin/jenkins-32150/directory-a/multi-file-in-subdir.txt src/test/resources/warnings_plugin/jenkins-32150/directory-a/subdir/file1 src/test/resources/warnings_plugin/jenkins-32150/directory-b/multi-file-in-subdir.txt src/test/resources/warnings_plugin/jenkins-32150/directory-b/subdir/file2 src/test/resources/warnings_plugin/jenkins-32150/file.txt http://jenkins-ci.org/commit/acceptance-test-harness/cee24aa85bec9ca281ba2762459d17e0cbe1da2b Log: JENKINS-32150 Added acceptance test that verifies resolving of paths by scanning the whole workspace. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30304) Footer hides trend graph links
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30304 Re: Footer hides trend graph links Code changed in jenkins User: Ulli Hafner Path: src/test/java/plugins/AbstractAnalysisTest.java http://jenkins-ci.org/commit/acceptance-test-harness/f3b8c7c2b2b642b2d48e32c048fc08e3751a13d5 Log: JENKINS-30304 Removed workaround for Jenkins releases < 1.640. (LTS is now at 1.642) Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/7a98fbe70123...f3b8c7c2b2b6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33190) build marked as failed if JUnitResultArchiver finds test failure reports in parallel steps
Title: Message Title
Steffen Pingel created an issue
Jenkins / JENKINS-33190
build marked as failed if JUnitResultArchiver finds test failure reports in parallel steps
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
26/Feb/16 10:21 PM
Priority:
Minor
Reporter:
Steffen Pingel
Steps: 1. Create a pipeline build with at least 2 parallel steps that both run tests of which some are failing 2. Run the pipeline
The build result is reported as "Finished: FAILURE" even though is expected to be "Finished: UNSTABLE".
The error on the console is reported as "None of the test reports contained any result" which is misleading. The test failures are shown under the test results of the job.
The error does not occur if there is only one parallel step (which of course isn't very useful).
Example pipeline:
def tests = [
'tests1':{
node {
sh 'mvn verify'
step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])
}
},
'tests2':{
node {
sh 'mvn verify'
step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])
}
}]
parallel tests
Error message on console:
[JIRA] [core] (JENKINS-23378) Raise minimum requirement to servlet 3.1
Title: Message Title SCM/JIRA link daemon commented on JENKINS-23378 Re: Raise minimum requirement to servlet 3.1 Code changed in jenkins User: Kohsuke Kawaguchi Path: war/src/main/webapp/WEB-INF/web.xml http://jenkins-ci.org/commit/jenkins/76c4c121a3b5fdeec9138ac463a33df911c378e5 Log: JENKINS-23378 accept any user with any role not just those who have one of the roles defined in this web.xml The special role name $B!H (B* $B!I (B is a shorthand for all role names defined in the deployment descriptor. The special role name $B!H (B** $B!I (B is a shorthand for any authenticated user independent of role. When the special role name $B!H (B** $B!I (B appears in an authorization constraint, it indicates that any authenticated user, independent of role, is authorized to perform the constrained requests. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012
Title: Message Title mocsharp updated an issue Jenkins / JENKINS-33164 Pipeline bat stuck on Windows Server 2012 Change By: mocsharp Component/s: ec2-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [wildfly-deployer-plugin] (JENKINS-33065) "WAR/EAR files" filepath gets truncated to filename after build
Title: Message Title Philipp Renoth commented on JENKINS-33065 Re: "WAR/EAR files" filepath gets truncated to filename after build One possible workaround is to start a bash command before to move the war/ear file to root and deploy it then without a path. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31094) Proposal: Jenkins Configuration DSL
Title: Message Title Joshua Hoblitt commented on JENKINS-31094 Re: Proposal: Jenkins Configuration DSL My $day_job uses puppet to manage Jenkins deployment, which is invaluable for being able to "test" the ci system. I am a strong "configuration management" proponent and a co-maintainer of the puppet-jenkins module. I have been working on managing jenkins' configuration state by quasi-serializing constructor parameters as JSON snippets passed in and out via the CLI jar and gave a puppetconf presentation on this effort titled Puppet vs. Jenkins. Perhaps needless to say, I have fairly well developed opinions about what makes an application easy to manage from a CM perspective. I have only briefly looked at the system-config-dsl plugin, so my comments are intended to be of a general nature rather than addressed to a specific implementation. While I can certainly see the utility of a groovy based DSL for complex configuration scenarios, I see this as more of a CM tool unto itself rather than a a good interface for puppet/chef/salt/etc. style CM engine. The fundamental concern I have is that this approach is "configuration as code" rather than "configuration as data". This makes it very difficult to introspect on and modify the configuration state in a meaningful way. One of the [perhaps poor] bits of advice I give when attempting to explain what makes a good CM integration, is to think about the module as presenting a native configuration API for the application rather than merely restoring state. This stems from the fact that most of the time, the CM end-user doesn't actually want to manage all of the state of an application. Typically, what they want to do is selectively manage state they care about while not disturbing defaults, boilerplate, or values of unknown function that may even change between application versions. It is, more(1) or less(2), possible to manage the configuration of jenkins by duplicating and resorting the xstream object dumps (1 for the moment, I am ignoring the issue of plugin management, which is its own nightmare; 2 less in that there are often minor changes between plugin versions that require opening the configuration and re-saving it and this completely breaks for encrypted values). The principle issues with the xstream dumps, from the CM point of view, is that the value of internal fields may be mangled in some way that is difficult to reproduce, are difficult for an end user to predict, are unstable (even white-space occasionally changes between core releases), and is it difficult to impossible predict which file a configuration value when end up and what the name of that file may be (eg, the dump file name for plugins), and that the semantics of no two XML documents are the same. The advantage of a configuration DSL over the xstream serialization, is that it will likely be much easier for an end-user highly familiar with the Jenkins internal APIs to reason directly in it rather than having to dump out a known state and store it away. The downside is, it isn't any easier, perhaps even harder, for a CM engine to express a management API and then dynamically generate the configuration. This means a CM interface will likely have to resort to shuffling opaque files around without any semantic understanding of the contents – that isn't an improvement over doing the same thing with xstream dumps. IMHO - the best [filesystem based] interface for a CM system is one that uses a well defined data/serialization format, allows the configuration to be split across multiple files in the now common foo.d style, and uses either extremely predictable file names (eg /etc/foo.conf), in
[JIRA] [s3-plugin] (JENKINS-30233) S3 sync rather than simple updoad
Title: Message Title Daniel Lafraia commented on JENKINS-30233 Re: S3 sync rather than simple updoad I would threat this more like a feature than a bug. Considering the number of artifacts, a build with many artifacts would benefit from this. Also, with Amazon's versioning it's better to have only changed files as new versions. FYI: AWS CLI does have a sync feature that could be used as a source of ideas for this feature http://docs.aws.amazon.com/cli/latest/reference/s3/sync.html I would feel much more comfortable if we had a sync feature within this plugin. Something like: [ ] Upload only modified files Compare object content Compare object date/time (bad for distributed builds) Compare object size This could be done by checking file size (AWS CLI has --size-only) or a safer method would be to download the object, compare it and upload only if it has changed. In this case a "GetObject" permission would be required. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3-plugin] (JENKINS-30233) S3 sync rather than simple updoad
Title: Message Title Daniel Lafraia updated an issue Jenkins / JENKINS-30233 S3 sync rather than simple updoad Change By: Daniel Lafraia Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-27548) Sporadic IOException: Failed to persist config
Title: Message Title eguess74 commented on JENKINS-27548 Re: Sporadic IOException: Failed to persist config Small update: for now the workaround of adding xercesImpl.jar to the classpath seems to be holding up. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp-plugin] (JENKINS-33189) When uploading multiple, don't error out if 1 fails
Title: Message Title Brantone created an issue Jenkins / JENKINS-33189 When uploading multiple, don't error out if 1 fails Issue Type: New Feature Assignee: Unassigned Components: hockeyapp-plugin Created: 26/Feb/16 8:44 PM Priority: Major Reporter: Brantone In the case where numerous packages are being uploaded (ex: specifying a folder of packages), the plugin will fail when error encountered, halting any chance of other packages uploading. Would be nice to continue on with other packages, but still throw failure. Add Comment
[JIRA] [hockeyapp-plugin] (JENKINS-24218) HockeyApp Plugin Authentication Error after jenkins restart
Title: Message Title Brantone commented on JENKINS-24218 Re: HockeyApp Plugin Authentication Error after jenkins restart Is this related to https://issues.jenkins-ci.org/browse/JENKINS-26907 ?? No action for year and a half, this is candidate for closing. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-33187) Manual Job Trigger Broken when triggering from Build Pipeline Plugin
Title: Message Title Matthew Adams updated an issue Jenkins / JENKINS-33187 Manual Job Trigger Broken when triggering from Build Pipeline Plugin Change By: Matthew Adams Environment: Manual Job Trigger Broken in Pipeline v1.5.1 with Jenkins 1.642.1 OS = Centos7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
John Leach commented on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Ah, this looks much better with 1.6.5. I now no longer have to set $ {WORKSPACE}/Dockerfile - I can set just Dockerfile. Thanks! But it's worth noting that I now CANNOT set ${WORKSPACE}
/Dockerfile. If I do that, it errors like this:
{{Your project is missing a Dockerfile [ssh-agent] Stopped. FATAL: Interrupted java.lang.RuntimeException: Interrupted at com.cloudbees.jenkins.plugins.docker_build_env.DockerBuildWrapper.setUp(DockerBuildWrapper.java:171) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [wildfly-deployer-plugin] (JENKINS-33065) "WAR/EAR files" filepath gets truncated to filename after build
Title: Message Title Todd Brady commented on JENKINS-33065 Re: "WAR/EAR files" filepath gets truncated to filename after build We are also having this issue. Our ear/war files are in directory build/FILE.ear So we put 'build/filename1.ear' in the configuration. Occasionally the input field is then set to 'filename1.ear' and our next build fails. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-31154) 2.0: provide better workflow visualization out of the box
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-31154 2.0: provide better workflow visualization out of the box Change By: Sam Van Oort Component/s: pipeline-stage-view-plugin Component/s: workflow-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-27152) Store sh control files outside of workspace
Title: Message Title Jesse Glick commented on JENKINS-27152 Re: Store sh control files outside of workspace Should also have a Pipeline step akin to pwd but for this temporary location, to make it easy to add other temporary files with custom meanings. Maybe even File.createTempFile semantics as an option. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cmakebuilder-plugin] (JENKINS-32657) cmakebuilder should allow cmake scripting
Title: Message Title Martin Weber commented on JENKINS-32657 Re: cmakebuilder should allow cmake scripting It is safe. The fix in 2.4.1 just renames the tags, nothing more Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-26210) Configure Jobs to be hidden from the delivery pipeline
Title: Message Title Suresh Kumar commented on JENKINS-26210 Re: Configure Jobs to be hidden from the delivery pipeline Pull Request for this change has submiited Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33188) Clean up pipeline-stage-view-poms
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-33188 Clean up pipeline-stage-view-poms Issue Type: Improvement Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 26/Feb/16 7:29 PM Priority: Minor Reporter: Sam Van Oort Switch to use 2.x parent pom (root `pom.xml` should contain no dependencies after) For example, see https://github.com/jenkinsci/github-branch-source-plugin/pull/16 Remove `workflow-aggregator` dependency, at least in `compile` scope. For `test` scope, could keep it, or replace with a more selective list. Remove the common deps, have the needful in the REST API, and then rely on that that to supply libraries for the UI Declare `workflow-job` dep in `pipeline-rest-api` POM; optionally declare it in `pipeline-stage-view` POM
[JIRA] [git-plugin] (JENKINS-22510) Clean After Checkout Results in Failed to Checkout Revision
Title: Message Title Mark Waite commented on JENKINS-22510 Re: Clean After Checkout Results in Failed to Checkout Revision One is not better than the other (as far as I can tell). You're correct that "Clean after checkout" was the first clean behavior, and was implemented very early in the development of the plugin. The specific benefit sought by the original submitter of the bug report was to better handle clean after a recursive submodule checkout had left the repository in a "dirty" state. In the submodule case, performing the clean before the checkout seems to have a better chance of succeeding than performing the clean after the checkout. I assume one of the reasons for a better chance of success is that the recursive submodule checkout may fail due to the "dirty" state of the working directory, which then might prevent the "clean after" from even being executed. I assume the job DSL includes one and not the other because it was initially created when "clean after" was the only option available. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-32628) DSL script from configuration or file not treated equally
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32628 Re: DSL script from configuration or file not treated equally Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/DslScriptLoader.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/DslScriptLoaderSpec.groovy job-dsl-core/src/test/resources/java.dsl job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/ExecuteDslScriptsSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/f5405721b948444530ed0d79a78c953f3040f5fe Log: Merge pull request #764 from daspilker/ JENKINS-32628 JENKINS-32628 log warning when script name collides with package name Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/a93f9abab7e8...f5405721b948 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-32628) DSL script from configuration or file not treated equally
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32628 Re: DSL script from configuration or file not treated equally Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/DslScriptLoader.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/DslScriptLoaderSpec.groovy job-dsl-core/src/test/resources/java.dsl job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/ExecuteDslScriptsSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/109399e7311189768eb77bd9a7a2766ac60bd183 Log: log warning when script name collides with package name [FIXES JENKINS-32628] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-32628) DSL script from configuration or file not treated equally
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32628 DSL script from configuration or file not treated equally Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-33187) Manual Job Trigger Broken when triggering from Build Pipeline Plugin
Title: Message Title Matthew Adams created an issue Jenkins / JENKINS-33187 Manual Job Trigger Broken when triggering from Build Pipeline Plugin Issue Type: Bug Assignee: Unassigned Attachments: ManualBuildStackTrace Components: build-pipeline-plugin Created: 26/Feb/16 6:54 PM Environment: Manual Job Trigger Broken in Pipeline v1.5.1 with Jenkins 1.642.1 Priority: Blocker Reporter: Matthew Adams When Creating a manual trigger downstream of a pipeline flow, I get the attached error in the log when trying to trigger the manual step and the job never starts.
[JIRA] [promoted-builds-plugin] (JENKINS-8804) Can't set security role for promotion process locally to a job
Title: Message Title Bruno Henrique da Silva commented on JENKINS-8804 Re: Can't set security role for promotion process locally to a job Hi, sorry to intrude, but I tested the new version and have two observations: 1- Jenkins is giving me two options of "If the build is a release build" when I checked "Promote builds when ..." 2 - I dont know if I got it right, but this version should allow the authorization of promote through roles? Because I tried and didn't work. Thanks, Bruno Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33110) Log details are not shown
Title: Message Title Jesse Glick commented on JENKINS-33110 Re: Log details are not shown Easily reproduced in jenkinsci/workflow-demo:1.14-2. Browser console shows No "data-stageId" on stage. Also, the build history widget does not update build #1 to remove the progress bar even after the build completes, unless you reload the page (#2 is updated properly); not sure if that is related to this bug or not. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33110) Log details are not shown
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-33110 Log details are not shown Change By: Sam Van Oort Assignee: Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-33186) Upgrade to Jenkins 1.642.1 from 1.594
Title: Message Title Shailesh Ligade created an issue Jenkins / JENKINS-33186 Upgrade to Jenkins 1.642.1 from 1.594 Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 26/Feb/16 6:32 PM Environment: Redhat 6 tomcat 1.8.0.24 Priority: Major Reporter: Shailesh Ligade After upgrade, we are getting ERROR: JENKINS-18403 JDK 5 not supported to run Maven; retrying with slave Java and setting compile/test properties to point to /jrockit-jdk1.6.0_45-R28.2.7-4.1.0 and Java switches to 1.8.0_45 I saw that both 1.594 and 1.642 were compiled against the same java, so why I am getting this message? What change is causing this error? Thanks S
[JIRA] [workflow-plugin] (JENKINS-31154) 2.0: provide better workflow visualization out of the box
Title: Message Title Sam Van Oort commented on JENKINS-31154 Re: 2.0: provide better workflow visualization out of the box The plugin is now available via the main update center, we are currently migrating issues/docs content over and bringing the Wiki into full compliance. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudtest-plugin] (JENKINS-30907) SOASTA CloudTest Plugin ignores "No Proxy Host" configuration
Title: Message Title Lance Tyler closed an issue as Fixed This issue has been fixed in the 2.22 version of the CloudTest plugin Jenkins / JENKINS-30907 SOASTA CloudTest Plugin ignores "No Proxy Host" configuration Change By: Lance Tyler Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-22510) Clean After Checkout Results in Failed to Checkout Revision
Title: Message Title mcrooney commented on JENKINS-22510 Re: Clean After Checkout Results in Failed to Checkout Revision Thanks Mark! I guess my takeaway from this is: "clean after was originally the only cleaning behavior, is the only one offered by job-dsl, and should generally work. Use clean before if clean after isn't working for you." Though, that's pretty ambiguous. I still don't totally understand myself, except that that understanding was enough for me to decide to use "after". What does "after" solve that "before" doesn't? Is "before" strictly better? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32548) Support for mercurial repositories
Title: Message Title
Jose Luis Rivero edited a comment on JENKINS-32548
Re: Support for mercurial repositories
Build the current master branch of the repo and [ tested in Jenkins 1.625.3 ](http://build.osrfoundation.org/view/All/job/sdformat-ci-pr_any-trusty-amd64_test_status/25/console) , fails with this backtrace:{code:java}Bitbucket notify on start failed: nulljava.lang.NullPointerException at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.createBuildStatusResourceFromBuild(BitbucketBuildStatusNotifier.java:169) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.prebuild(BitbucketBuildStatusNotifier.java:78) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:840) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:835) at hudson.model.Build$BuildExecution.doRun(Build.java:144) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32548) Support for mercurial repositories
Title: Message Title
Jose Luis Rivero edited a comment on JENKINS-32548
Re: Support for mercurial repositories
Build the current master branch of the repo and [tested in Jenkins 1.625.3 ]( | http://build.osrfoundation.org/view/All/job/sdformat-ci-pr_any-trusty-amd64_test_status/25/console ) ] , fails with this backtrace:{code:java}Bitbucket notify on start failed: nulljava.lang.NullPointerException at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.createBuildStatusResourceFromBuild(BitbucketBuildStatusNotifier.java:169) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.prebuild(BitbucketBuildStatusNotifier.java:78) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:840) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:835) at hudson.model.Build$BuildExecution.doRun(Build.java:144) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
Patrick Wolf created an issue
Jenkins / JENKINS-33185
Visualize parallel steps within a Pipeline Stage
Issue Type:
Story
Assignee:
Antonio Muñiz
Attachments:
parallel.png
Components:
pipeline-stage-view-plugin
Created:
26/Feb/16 6:01 PM
Priority:
Minor
Reporter:
Patrick Wolf
1) Parallel steps are the common workflow case 2) Build logs for parallel steps are not informative 3) A user would expect Stage View to somehow address the issue
Current state:
stage declarations within parallel sections are not being considered as parallel
steps within one parallelized step are being mixed => no info in the view (see the screenshot)
Test script (move stage declarations where you want):
for (int i=0; i< 2; ++i) {
stage "Stage #"+i
print 'Hello, world
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32548) Support for mercurial repositories
Title: Message Title Jose Luis Rivero commented on JENKINS-32548 Re: Support for mercurial repositories Build the current master branch of the repo and tested in Jenkins 1.625.3, fails with this backtrace: Bitbucket notify on start failed: null java.lang.NullPointerException at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.createBuildStatusResourceFromBuild(BitbucketBuildStatusNotifier.java:169) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.prebuild(BitbucketBuildStatusNotifier.java:78) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:840) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:835) at hudson.model.Build$BuildExecution.doRun(Build.java:144) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33184) JobDSL plugin requires build-publisher plugin to use discardOldBuilds
Title: Message Title
Benjamin van den Berg updated an issue
Jenkins / JENKINS-33184
JobDSL plugin requires build-publisher plugin to use discardOldBuilds
Change By:
Benjamin van den Berg
I configured a mavenJob to discard old builds:{ { code} mavenJob(name) {...publishers {publishBuild {discardOldBuilds(-1, 20)}}} {code } } I get a warning in the console logs, and the DSL job is unstable, because it requires version 1.20 of the build-publisher plugin. However, the Maven job is created with the "Discard old builds" correctly set.My guess is that discarding old builds no longer requires the build-publisher plugin, and it should not be under the PublishBuildContext:{ { code} @RequiresPlugin(id = 'build-publisher', minimumVersion = '1.20')void publishBuild(@DslContext(PublishBuildContext) Closure contextClosure = null) {PublishBuildContext publishBuildContext = new PublishBuildContext()ContextHelper.executeInContext(contextClosure, publishBuildContext)publisherNodes << new NodeBuilder().'hudson.plugins.build__publisher.BuildPublisher' {publishUnstableBuilds(publishBuildContext.publishUnstable)publishFailedBuilds(publishBuildContext.publishFailed)if (publishBuildContext.discardOldBuilds) {logRotator {daysToKeep(publishBuildContext.daysToKeep)numToKeep(publishBuildContext.numToKeep)artifactDaysToKeep(publishBuildContext.artifactDaysToKeep)artifactNumToKeep(publishBuildContext.artifactNumToKeep)}}}} {code } }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-33184) JobDSL plugin requires build-publisher plugin to use discardOldBuilds
Title: Message Title
Benjamin van den Berg created an issue
Jenkins / JENKINS-33184
JobDSL plugin requires build-publisher plugin to use discardOldBuilds
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
26/Feb/16 5:53 PM
Environment:
Job DSL plugin version: 1.43 Jenkins version: 1.632 Hudson Build Publisher plugin not installed
Priority:
Minor
Reporter:
Benjamin van den Berg
I configured a mavenJob to discard old builds:
{{ mavenJob(name) { ... publishers { publishBuild { discardOldBuilds(-1, 20) }
} } }}
I get a warning in the console logs, and the DSL job is unstable, because it requires version 1.20 of the build-publisher plugin. However, the Maven job is created with the "Discard old builds" correctly set.
My guess is that discarding old builds no longer requires the build-publisher plugin, and it should not be under the PublishBuildContext:
{{ @RequiresPlugin(id = 'build-publisher', minimumVersion = '1.20') void publishBuild(@DslContext(PublishBuildContext) Closure contextClosure = null) { PublishBuildContext publishBuildContext = new PublishBuildContext() ContextHelper.executeInContext(contextClosure, publishBuildContext)
[JIRA] [git-plugin] (JENKINS-22510) Clean After Checkout Results in Failed to Checkout Revision
Title: Message Title Mark Waite commented on JENKINS-22510 Re: Clean After Checkout Results in Failed to Checkout Revision That would be fine. I'm not sure how you'll make the help text describe the things you have learned, but you'll make my life easier evaluating your proposed changes if you submit your proposed change as a pull request. You can do that by: Create a free GitHub account for yourself Fork the git plugin repository with the "Fork" button on the left of the repo Edit the help text (from the web interface is easy enough) in your forked copy of the repository (https://github.com/YourUserNameGoesHere/git-plugin/blob/master/src/main/resources/hudson/plugins/git/extensions/impl/CleanBeforeCheckout/help.html and https://github.com/YourUserNameGoesHere/git-plugin/blob/master/src/main/resources/hudson/plugins/git/extensions/impl/CleanCheckout/help.html) Save your changes (from the web Submit a pull request (using the GitHub submit pull request from the web) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] [git-plugin] (JENKINS-22510) Clean After Checkout Results in Failed to Checkout Revision
Title: Message Title mcrooney commented on JENKINS-22510 Re: Clean After Checkout Results in Failed to Checkout Revision "Relying on the user to know when they should select "clean before checkout" and when they should "clean after checkout" seems like we're expecting too much from the users." Totally, I agree, I ended up having to search on Google and then read through this bug report, to figure out what the difference was, and I'm still not sure I understand what the difference would be using one or the other. The root of this problem is that the help texts for these checkboxes are exactly the same except for the word "before" and "after" I'm happy to file an issue for improving the help texts if that seems reasonable? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-32788) Get build failure analyzer result using rest api
Title: Message Title
James Nord closed an issue as Not A Defect
This is already implemented. You just need to call the API correctly to get the amount of detail you require.
e.g.
${JENKINS_URL}/job///api/xml?depth=2}
${JENKINS_URL}/job///api/xml?tree=actions[foundFailureCauses[*]]
Jenkins / JENKINS-32788
Get build failure analyzer result using rest api
Change By:
James Nord
Status:
Open Closed
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [plugin-proposals] (JENKINS-28164) Provide creation date of job
Title: Message Title davehorner commented on JENKINS-28164 Re: Provide creation date of job a core piece of data and should not require a plugin and the necessary extension points do not always return good data. I mentioned sometimes jobs are returning with no jobConfigHistory, I still have yet to understand why. I would love to see this get implemented in core. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-33183) Anonymous scan credentials causes checkout to fail
Title: Message Title
Andy Neebel updated an issue
Jenkins / JENKINS-33183
Anonymous scan credentials causes checkout to fail
Change By:
Andy Neebel
I am getting an error when I have my credentials set to none or anonymous. The branch indexing works properly and automatically finds new PR's when they are created, but the builds themselves fail because the checkout command doesn't seem to be willing to run without specific credentials.{ { noformat} No scan credentials, skippingERROR: Could not determine exact tip revision of PR-5; falling back to nondeterministic checkout > C:\Program Files\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10Fetching changes from 2 remote Git repositories > C:\Program Files\Git\bin\git.exe config remote.origin.url https:////.git # timeout=10Fetching upstream changes from https:////.git > C:\Program Files\Git\bin\git.exe --version # timeout=10 > C:\Program Files\Git\bin\git.exe -c core.askpass=true fetch --tags --progress https:////.git +refs/heads/*:refs/remotes/origin/* > C:\Program Files\Git\bin\git.exe config remote.origin1.url https:////.git # timeout=10Fetching upstream changes from https:////.git > C:\Program Files\Git\bin\git.exe -c core.askpass=true fetch --tags --progress https:////.git +refs/pull/*/merge:refs/remotes/origin/pr/*Seen branch in repository origin/masterSeen branch in repository origin/pr/1Seen branch in repository origin/pr/2Seen branch in repository origin/pr/5Seen 4 remote branchesERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE {noformat } } Based on reading some other issues, it appears to me that anonymous access was intentionally left unusable due to concerns with API rate limiting. There also appeared to be a comment that the rate limiting doesn't apply to a Github Enterprise Server, which is what I'm using here. I understand discouraging people from using anonymous access, but right now it appears to work correctly for indexing and then break during checkout. Can similar logic to what happens during indexing be added to the checkout to allow anonymous to get the revision to checkout?From reading the code it appears that the function {{retrieve(SCMHead, TaskListener)}} needs to have functionality closer to that of {{retrieve(SCMHeadObserver, TaskListener)}} Also, should {{retrieve(SCMHead, TaskListener)}} be using the checkout credentials instead of the scan credentials? Either way, I think it should allow anonymous credentials to be used.
Add Comment
[JIRA] [github-branch-source-plugin] (JENKINS-33183) Anonymous scan credentials causes checkout to fail
Title: Message Title
Andy Neebel created an issue
Jenkins / JENKINS-33183
Anonymous scan credentials causes checkout to fail
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
github-branch-source-plugin
Created:
26/Feb/16 4:27 PM
Environment:
Jenkins 1.625.3, GitHub Branch Source Plugin 1.2, GitHub Enterprise
Priority:
Minor
Reporter:
Andy Neebel
I am getting an error when I have my credentials set to none or anonymous. The branch indexing works properly and automatically finds new PR's when they are created, but the builds themselves fail because the checkout command doesn't seem to be willing to run without specific credentials.
{{ No scan credentials, skipping ERROR: Could not determine exact tip revision of PR-5; falling back to nondeterministic checkout > C:\Program Files\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10 Fetching changes from 2 remote Git repositories > C:\Program Files\Git\bin\git.exe config remote.origin.url https:.git # timeout=10 Fetching upstream changes from https:.git > C:\Program Files\Git\bin\git.exe --version # timeout=10 > C:\Program Files\Git\bin\git.exe -c core.askpass=true fetch --tags --progress https:.git +refs/heads/:refs/remotes/origin/ > C:\Program Files\Git\bin\git.exe config remote.origin1.url https:.git # timeout=10 Fetching upstream changes from https:.git >
[JIRA] [workflow-plugin] (JENKINS-27039) Option for input or stage step to cancel older executions
Title: Message Title
Jesse Glick commented on JENKINS-27039
Re: Option for input or stage step to cancel older executions
A vague thought: we could have a step called, say, milestone (checkpoint would be natural but it is already taken), taking a natural number argument. Unlike stage names, which have no order beyond what is discovered as you run, builds would be required to pass through milestones in increasing order (perhaps allowing some builds to skip inapplicable milestones?), and an older build would not be allowed to pass a given milestone after a newer build hit it. Details TBD.
For purposes of the stage view and other UI, we could keep stage as is, or just deprecate it altogether and go with a block-scoped step as is proposed in JENKINS-26107.
Rough sketch:
label('Building') {
node {
checkout scm
sh 'make'
stash 'stuff'
}
}
milestone 1
label('Testing') {
node {
unstash 'stuff'
sh 'make test'
}
}
milestone 2
/* optionally:
input 'OK to publish?'
milestone 3
*/
label('Publishing') {
node {
unstash 'stuff'
sh 'scp stuff …'
}
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-32835) abortAllJobs() for Multijob configured from Job DSL is not working
Title: Message Title Daniel Spilker commented on JENKINS-32835 Re: abortAllJobs() for Multijob configured from Job DSL is not working I can't reproduce this on 1.42. Can you post a complete (but minimal) script which reproduces the problem? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-18897) ssh-agent & slave: 'JCE cannot authenticate the provider BC', because 'Class is on the bootclasspath'
Title: Message Title Stan Towianski commented on JENKINS-18897 Re: ssh-agent & slave: 'JCE cannot authenticate the provider BC', because 'Class is on the bootclasspath' Hi. You can actually get it to work with a passphrase on your private key. see: https://issues.jenkins-ci.org/browse/JENKINS-32120 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-24658) ssh-agent fails with "JCE cannot authenticate the provider BC" on slave
Title: Message Title Stan Towianski commented on JENKINS-24658 Re: ssh-agent fails with "JCE cannot authenticate the provider BC" on slave Hi. You can actually get it to work with a passphrase on your private key. see: https://issues.jenkins-ci.org/browse/JENKINS-32120 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-33182) Checking "This build is parameterized" but having no parameters throws a NullPointerException
Title: Message Title
Kevin R. updated an issue
Jenkins / JENKINS-33182
Checking "This build is parameterized" but having no parameters throws a NullPointerException
Change By:
Kevin R.
h2. To Reproduce* have job configured to accept webhook from repo* check off "This build is parameterized", save* trigger webhookh2. Screenshot!http://i.imgur.com/mkoXCuK.jpg!h2. StackTrace{code:title=stacktrace.text|borderStyle=solid}java.lang.NullPointerException at org.jenkinsci.plugins.ghprb.GhprbTrigger.getDefaultParameters(GhprbTrigger.java:385) at org.jenkinsci.plugins.ghprb.GhprbTrigger.startJob(GhprbTrigger.java:253) at org.jenkinsci.plugins.ghprb.GhprbBuilds.build(GhprbBuilds.java:67) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.build(GhprbPullRequest.java:263) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.tryBuild(GhprbPullRequest.java:255) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.check(GhprbPullRequest.java:158) at org.jenkinsci.plugins.ghprb.GhprbRepository.onIssueCommentHook(GhprbRepository.java:308) at org.jenkinsci.plugins.ghprb.GhprbWebHook.handleComment(GhprbWebHook.java:52) at org.jenkinsci.plugins.ghprb.GhprbRootAction.doIndex(GhprbRootAction.java:117) at sun.reflect.GeneratedMethodAccessor517.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$2.dispatch(MetaClass.java:165) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) 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:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:200) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] [git-client-plugin] (JENKINS-33174) Support API token as credentials for git https (GitHub...)
Title: Message Title Cyrille Le Clerc commented on JENKINS-33174 Re: Support API token as credentials for git https (GitHub...) Mark Waite when I discussed with Jesse Glick, I imagined that we could enhance the behavior of the "add credentials" button in the job config page to inject a default domain and to restrict the type of credentials to match what the plugin declaring the "add credentials button" supports. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Stan Towianski commented on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" [ssh-agent] Using credentials myUser (with private key and passphrase) [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Java/JNR ssh-agent [ssh-agent] Unable to read key: exception using cipher - please check password and data. org.bouncycastle.openssl.EncryptionException: exception using cipher - please check password and data. at org.bouncycastle.openssl.PEMUtilities.crypt(Unknown Source) at org.bouncycastle.openssl.PEMUtilities.crypt(Unknown Source) at org.bouncycastle.openssl.PEMReader$KeyPairParser.readKeyPair(Unknown Source) at org.bouncycastle.openssl.PEMReader$RSAKeyPairParser.parseObject(Unknown Source) at org.bouncycastle.openssl.PEMReader.readObject(Unknown Source) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.addIdentity(JNRRemoteAgent.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:608) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.SecurityException: JCE cannot authenticate the provider BC at javax.crypto.Cipher.getInstance(Cipher.java:657) ... 21 more Caused by: java.util.jar.JarException: Class is on the bootclasspath These are are related as far as I can tell. A teammate figured out Bouncy Castle problem has to be done on a build slave if you are using those. I'm not sure if it needs to be done on the Jenkins master too, but I did it there first already. I think java 6 does not work with newer Jenkins? I did not test fix with java 7. I used Java 8 add these 4 jar files here: /…./java/jdk/jdk-1.8u66/jre/lib/ext rw-r r - 1 root root 2070477 Feb 25 16:46 bcprov-ext-jdk15on-147.jar rw-r r - 1 root root 1997327 Feb 25 16:46 bcprov-jdk15on-147.jar /…./java/jdk/jdk-1.8u66/jre/lib/security rw-r r - 1
[JIRA] [ghprb-plugin] (JENKINS-33182) Checking "This build is parameterized" but having no parameters throws a NullPointerException
Title: Message Title
Kevin R. updated an issue
Jenkins / JENKINS-33182
Checking "This build is parameterized" but having no parameters throws a NullPointerException
Change By:
Kevin R.
h2. Screenshot!http://i.imgur.com/mkoXCuK.jpg!h2. StackTrace{ { code:title=stacktrace.text|borderStyle=solid} java.lang.NullPointerException at org.jenkinsci.plugins.ghprb.GhprbTrigger.getDefaultParameters(GhprbTrigger.java:385) at org.jenkinsci.plugins.ghprb.GhprbTrigger.startJob(GhprbTrigger.java:253) at org.jenkinsci.plugins.ghprb.GhprbBuilds.build(GhprbBuilds.java:67) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.build(GhprbPullRequest.java:263) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.tryBuild(GhprbPullRequest.java:255) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.check(GhprbPullRequest.java:158) at org.jenkinsci.plugins.ghprb.GhprbRepository.onIssueCommentHook(GhprbRepository.java:308) at org.jenkinsci.plugins.ghprb.GhprbWebHook.handleComment(GhprbWebHook.java:52) at org.jenkinsci.plugins.ghprb.GhprbRootAction.doIndex(GhprbRootAction.java:117) at sun.reflect.GeneratedMethodAccessor517.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$2.dispatch(MetaClass.java:165) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) 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:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:200) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at
[JIRA] [ghprb-plugin] (JENKINS-33182) Checking "This build is parameterized" but having no parameters throws a NullPointerException
Title: Message Title
Kevin R. updated an issue
Jenkins / JENKINS-33182
Checking "This build is parameterized" but having no parameters throws a NullPointerException
Change By:
Kevin R.
h2. Screenshot!http://i.imgur.com/mkoXCuK.jpg!h2. StackTrace{{ java.lang.NullPointerException at org.jenkinsci.plugins.ghprb.GhprbTrigger.getDefaultParameters(GhprbTrigger.java:385) at org.jenkinsci.plugins.ghprb.GhprbTrigger.startJob(GhprbTrigger.java:253) at org.jenkinsci.plugins.ghprb.GhprbBuilds.build(GhprbBuilds.java:67) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.build(GhprbPullRequest.java:263) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.tryBuild(GhprbPullRequest.java:255) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.check(GhprbPullRequest.java:158) at org.jenkinsci.plugins.ghprb.GhprbRepository.onIssueCommentHook(GhprbRepository.java:308) at org.jenkinsci.plugins.ghprb.GhprbWebHook.handleComment(GhprbWebHook.java:52) at org.jenkinsci.plugins.ghprb.GhprbRootAction.doIndex(GhprbRootAction.java:117) at sun.reflect.GeneratedMethodAccessor517.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$2.dispatch(MetaClass.java:165) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) 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:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:200) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at
[JIRA] [ghprb-plugin] (JENKINS-33182) Checking "This build is parameterized" but having no parameters throws a NullPointerException
Title: Message Title
Kevin R. updated an issue
Jenkins / JENKINS-33182
Checking "This build is parameterized" but having no parameters throws a NullPointerException
Change By:
Kevin R.
h2. Screenshot!http://i.imgur.com/mkoXCuK.jpg!h2. StackTrace{{ java.lang.NullPointerException at org.jenkinsci.plugins.ghprb.GhprbTrigger.getDefaultParameters(GhprbTrigger.java:385) at org.jenkinsci.plugins.ghprb.GhprbTrigger.startJob(GhprbTrigger.java:253) at org.jenkinsci.plugins.ghprb.GhprbBuilds.build(GhprbBuilds.java:67) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.build(GhprbPullRequest.java:263) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.tryBuild(GhprbPullRequest.java:255) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.check(GhprbPullRequest.java:158) at org.jenkinsci.plugins.ghprb.GhprbRepository.onIssueCommentHook(GhprbRepository.java:308) at org.jenkinsci.plugins.ghprb.GhprbWebHook.handleComment(GhprbWebHook.java:52) at org.jenkinsci.plugins.ghprb.GhprbRootAction.doIndex(GhprbRootAction.java:117) at sun.reflect.GeneratedMethodAccessor517.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$2.dispatch(MetaClass.java:165) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) 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:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:200) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at
[JIRA] [ghprb-plugin] (JENKINS-33182) Checking "This build is parameterized" but having no parameters throws a NullPointerException
Title: Message Title
Kevin R. created an issue
Jenkins / JENKINS-33182
Checking "This build is parameterized" but having no parameters throws a NullPointerException
Issue Type:
Bug
Assignee:
Honza Brázdil
Components:
ghprb-plugin
Created:
26/Feb/16 3:53 PM
Environment:
Jenkins 1.645 GHPR-Builder 1.298
Labels:
ghprb git
Priority:
Minor
Reporter:
Kevin R.
Screenshot
StackTrace
{{java.lang.NullPointerException at org.jenkinsci.plugins.ghprb.GhprbTrigger.getDefaultParameters(GhprbTrigger.java:385) at org.jenkinsci.plugins.ghprb.GhprbTrigger.startJob(GhprbTrigger.java:253) at org.jenkinsci.plugins.ghprb.GhprbBuilds.build(GhprbBuilds.java:67) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.build(GhprbPullRequest.java:263) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.tryBuild(GhprbPullRequest.java:255) at org.jenkinsci.plugins.ghprb.GhprbPullRequest.check(GhprbPullRequest.java:158) at
[JIRA] [job-dsl-plugin] (JENKINS-33176) Git clean() results in clean after, not before
Title: Message Title
Daniel Spilker edited a comment on JENKINS-33176
Re: Git clean() results in clean after, not before
The Git plugin changed the behaviour when switching to the 2.0 config format. The {{}} tag used to be pre-checkout, but that get got migrated to the {{CleanCheckout}} extension which runs after checkout, see https://github.com/jenkinsci/git-plugin/commit/7fbdbd47875386d524d78ef7c82722ff7fba18b8.I will deprecate the {{clean}} DSL method and add both extensions.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31706) ProcessTreeKiller broken for Windows when node went offline/online
Title: Message Title Pierre-Henri Cazes commented on JENKINS-31706 Re: ProcessTreeKiller broken for Windows when node went offline/online Error reproduced : Slave agent is launch by a script containing such command : javaws http://localhost:8080/jenkins/computer/NODE/slave-agent.jnlp Job consists in a Windows Batch command : notepad.exe. Analysis : When disconnecting node using the jenkins UI, the slave-agent is set disconnected and then it restarts. The submitting a new job and cancelling it with the UI causes an Error in Class hudson.util.ProcessTree method "public static ProcessTree get()" @line:355 java.lang.UnsatisfiedLinkError: Native Library C:\Users\\.jenkins\cache\jars\4A\winp.x64.22D9AB310A3FA2D96B6E03A836A47724.dll already loaded in another classloader When this Error is catched, ProcessTreeKiller enable static attribute is set to false, then DEFAULT ProcessTree imlementation is used, where killAll is no-op. So only ProcessRuntime running the cmd command is destroyed and only cmd process is killed (which doesn't kill the subprocesses) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33176) Git clean() results in clean after, not before
Title: Message Title Daniel Spilker commented on JENKINS-33176 Re: Git clean() results in clean after, not before The Git plugin changed the behaviour when switching to the 2.0 config format. The tag used to be pre-checkout, but that get migrated to the CleanCheckout extension which runs after checkout, see https://github.com/jenkinsci/git-plugin/commit/7fbdbd47875386d524d78ef7c82722ff7fba18b8. I will deprecate the clean DSL method and add both extensions. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33109) Log window appear at top of the page
Title: Message Title Antonio Muñiz assigned an issue to Unassigned Jenkins / JENKINS-33109 Log window appear at top of the page Change By: Antonio Muñiz Assignee: Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-33174) Support API token as credentials for git https (GitHub...)
Title: Message Title Mark Waite commented on JENKINS-33174 Re: Support API token as credentials for git https (GitHub...) My apologies, but I don't understand how your description is different from the current behavior. When I add a git repository to a job definition, the user interface only shows those credentials which match the domain specification of the repository which was added. If the domain specification limits the credential to hostname = "github.com", then only global credentials and credentials specified for "github.com" will be presented. The credentials assigned to the "bitbucket.org" domain or to the "gitlab.com" domain are not visible in that context. Can you further clarify what you're expecting to see change? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-32628) DSL script from configuration or file not treated equally
Title: Message Title Daniel Spilker commented on JENKINS-32628 Re: DSL script from configuration or file not treated equally The next version will log a warning to console output if a conflicting package name is detected. https://github.com/jenkinsci/job-dsl-plugin/pull/764 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32948) ["git" step] Add "WipeWorkspace" option to simplify release jobs
Title: Message Title
Cyrille Le Clerc commented on JENKINS-32948
Re: ["git" step] Add "WipeWorkspace" option to simplify release jobs
Could it make sense to declare at the workspace level a strategy to never reuse the workspace, always wipe out the workspace before entering the step?
it could look like:
ws (reuse:"never") {
git url: url: 'https://github.com/account/repo.git', credentialsId: 'github-credentials'
...
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-32481) git plugin does not retry when submodule update fails
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-32481 git plugin does not retry when submodule update fails Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-32479 multiple git repositories sometimes fail to checkout some of them into subdirectory Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-33174) Support API token as credentials for git https (GitHub...)
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-33174 Support API token as credentials for git https (GitHub...) Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32948) ["git" step] Add "WipeWorkspace" option to simplify release jobs
Title: Message Title Jesse Glick commented on JENKINS-32948 Re: ["git" step] Add "WipeWorkspace" option to simplify release jobs I recommend using the checkout step, which lets you customize the Git plugin however you like. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33181) Sleep step is being blocked by script-security when used outside a node step
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-33181 Sleep step is being blocked by script-security when used outside a node step Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 26/Feb/16 3:19 PM Priority: Major Reporter: Antonio Muñiz sleep 50 If sandbox is activated, this script fails: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method org.jenkinsci.plugins.workflow.cps.CpsScript sleep long Add Comment
[JIRA] [shelve-project-plugin] (JENKINS-12160) Add ability to shelve many projects at once
Title: Message Title Ajay Kumar commented on JENKINS-12160 Re: Add ability to shelve many projects at once +1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-33174) Support API token as credentials for git https (GitHub...)
Title: Message Title Mark Waite commented on JENKINS-33174 Re: Support API token as credentials for git https (GitHub...) I use credential domains already with my GitHub API token. I assign the GitHub user name and password to only be displayed for the domain "github.com" . It works quite well. I have it included in my Jenkins server docker image that I use for fast setup and teardown of interactive tests. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-33174) Support API token as credentials for git https (GitHub...)
Title: Message Title Cyrille Le Clerc commented on JENKINS-33174 Re: Support API token as credentials for git https (GitHub...) Thanks Mark Waite for the quick answer. > I create a new credential with my user name, and with the API token as the password, then reference that credential from the job definition. Does that not work for you? You are right, I forgot that we could store the token in the password field and use the account name as username. > Is there something more to be gained by calling the password an API token? I feel it would be more intuitive as GitHub call them tokens and not password and as my understanding is that GitHub API tokens don't require to provide a username. This question is more about the philosophy on how to filter credentials in Jenkins. I see benefits in adding more credentials types, Jesse Glick told me that his vision is to leverage credentials domains. I'll try to mockup different use cases. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33180) XHR HTTP 404 while trying to add post build action
Title: Message Title
starenka . created an issue
Jenkins / JENKINS-33180
XHR HTTP 404 while trying to add post build action
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
jenkins.png
Components:
core
Created:
26/Feb/16 2:53 PM
Environment:
jenkins 1.650 (see attachment)
Priority:
Minor
Reporter:
starenka .
I can't add any post build action as the XHR request (which probably spawns action form inside the page) yields HTTP404...
request:
http://192.168.1.231:8080/$stapler/bound/3507e2f0-5155-4025-b416-240f0bdf1fb9/render
{{POST /$stapler/bound/3507e2f0-5155-4025-b416-240f0bdf1fb9/render HTTP/1.1 Host: 192.168.1.231:8080 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Iceweasel/44.0.2 Accept: text/_javascript_, text/html, application/xml, text/xml, / Accept-Language: en-US,en;q=0.7,cs;q=0.3 Accept-Encoding: gzip, deflate DNT: 1 X-Requested-With:
[JIRA] [xcode-plugin] (JENKINS-33179) Only one Xcode step, needs to be many
Title: Message Title Keith Smith created an issue Jenkins / JENKINS-33179 Only one Xcode step, needs to be many Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 26/Feb/16 2:48 PM Priority: Blocker Reporter: Keith Smith Updated Jenkins and the XCode plugin, and now can no longer add more than one XCode Build Steps. My jobs compiles the code twice, using two different configurations and schemas. Please allow more than one XCode build step again. Add Comment
[JIRA] [workflow-plugin] (JENKINS-27039) Option for input or stage step to cancel older executions
Title: Message Title Antonio Muñiz commented on JENKINS-27039 Re: Option for input or stage step to cancel older executions There are more cases to consider, specially when the `input` step is not used and builds proceed without human interaction. Think of a Pipeline definition where the time taken by its stages is different from one build to another (for whatever reason), it could lead to older builds finishing (not in the stage but the full build) earlier than newer builds, so your continuous deployment configuration would be deploying an old state even having a newer one. Probably what it's needed is a way to force builds going in-order through the stage, if a build reaches the stage when a newer one is inside or has already passed through then it has to be aborted. Perhaps this is worth to go into a new specific step managing all concurrency stuff and leave `stage` as a labeling step. This feature in conjunction with the `linear` behavior described in previous comments (JENKINS-32829) would remove the need to manually cancel any order build (which was the initial motivation of this issue). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-33174) Support API token as credentials for git https (GitHub...)
Title: Message Title Mark Waite commented on JENKINS-33174 Re: Support API token as credentials for git https (GitHub...) The plugin already supports GitHub API tokens in its current steps. I create a new credential with my user name, and with the API token as the password, then reference that credential from the job definition. Does that not work for you? Is there something more to be gained by calling the password an API token? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-30868) Changes List in Project and Job is Displaying Last Change
Title: Message Title Prathap Subramanian resolved as Fixed Jenkins / JENKINS-30868 Changes List in Project and Job is Displaying Last Change Change By: Prathap Subramanian Status: In Progress Resolved Assignee: Jason Davis Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-30868) Changes List in Project and Job is Displaying Last Change
Title: Message Title Prathap Subramanian commented on JENKINS-30868 Re: Changes List in Project and Job is Displaying Last Change This issue is fixed and merged into the master as part of the pull request. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-6933) TFS plugin does not support the -proxy TFS switch.
Title: Message Title Olivier Dagenais assigned an issue to mikestack1677 Jenkins / JENKINS-6933 TFS plugin does not support the -proxy TFS switch. Change By: Olivier Dagenais Assignee: redsolo mikestack1677 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-6933) TFS plugin does not support the -proxy TFS switch.
Title: Message Title Olivier Dagenais resolved as Fixed This will be in release 4.1.0. Jenkins / JENKINS-6933 TFS plugin does not support the -proxy TFS switch. Change By: Olivier Dagenais Status: Open Resolved Assignee: Olivier Dagenais redsolo Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials Mikel Ortega there are two users telling that if you configure in a right way Additional credentials, svn:externals works fine. Additionally, I could not reproduce the bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-6933) TFS plugin does not support the -proxy TFS switch.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-6933 Re: TFS plugin does not support the -proxy TFS switch. Code changed in jenkins User: Olivier "Oli" Dagenais Path: pom.xml src/main/java/hudson/plugins/tfs/TeamFoundationServerScm.java src/main/java/hudson/plugins/tfs/commands/AbstractCallableCommand.java src/main/java/hudson/plugins/tfs/commands/ServerConfigurationProvider.java src/main/java/hudson/plugins/tfs/model/MockableVersionControlClient.java src/main/java/hudson/plugins/tfs/model/ModernConnectionAdvisor.java src/main/java/hudson/plugins/tfs/model/ModernHTTPClientFactory.java src/main/java/hudson/plugins/tfs/model/Server.java src/main/java/hudson/plugins/tfs/model/WebProxySettings.java src/test/java/hudson/plugins/tfs/FunctionalTest.java src/test/java/hudson/plugins/tfs/IntegrationTestHelper.java src/test/java/hudson/plugins/tfs/InterceptingTaskListener.java src/test/java/hudson/plugins/tfs/LoggingFiltersSourceAdapter.java src/test/java/hudson/plugins/tfs/commands/AbstractCallableCommandTest.java src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/config.xml src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/hudson.plugins.tfs.TeamFoundationServerScm.xml src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/identity.key.enc src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/jobs/useWebProxyServer/builds/2015-07-15_20-37-42/build.xml src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/jobs/useWebProxyServer/builds/2015-07-15_20-37-42/changelog.xml src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/jobs/useWebProxyServer/builds/2015-07-15_20-37-42/log src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/jobs/useWebProxyServer/builds/lastFailedBuild src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/jobs/useWebProxyServer/builds/lastStableBuild src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/jobs/useWebProxyServer/builds/lastSuccessfulBuild src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/jobs/useWebProxyServer/builds/lastUnstableBuild src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/jobs/useWebProxyServer/builds/lastUnsuccessfulBuild src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/jobs/useWebProxyServer/builds/legacyIds src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/jobs/useWebProxyServer/config.xml src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/jobs/useWebProxyServer/nextBuildNumber src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/proxy.xml src/test/resources/hudson/plugins/tfs/FunctionalTest/useWebProxyServer/secret.key http://jenkins-ci.org/commit/tfs-plugin/2fb117505b6d4b45e5c883e8045d182c886a86de Log: Merge pull request #72 from jenkinsci/handle_proxy_settings JENKINS-6933 Handle proxy settings Compare: https://github.com/jenkinsci/tfs-plugin/compare/dfe4480fa7ac...2fb117505b6d Add Comment
[JIRA] [subversion-plugin] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Mikel Ortega commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials I don't know why it's closed. I'm trying to configure the way the you explain but it doesn't work. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-29598) p4 polling doesn't trigger workflow
Title: Message Title David Schott commented on JENKINS-29598 Re: p4 polling doesn't trigger workflow Thanks Rick! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials Alexander Rudnev Because there is not a bug but some things to improve. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth-plugin] (JENKINS-33098) Build Queue/Build Executor Status disappears
Title: Message Title John V closed an issue as Fixed No longer reproducible after upgrading to the latest version Jenkins / JENKINS-33098 Build Queue/Build Executor Status disappears Change By: John V Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33110) Log details are not shown
Title: Message Title Russell Gallop commented on JENKINS-33110 Re: Log details are not shown Pipeline DSL examples. With 1 step the stage-logs are expanded (but won't contract) e.g.: stage 'test' echo 'Foo' With > 1 step the stage-logs are folded up (and won't expand) e.g.: stage 'test' echo 'Foo' echo 'Bar' Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-33178) Build pipeline displays incorrectly when triggering the same project multiple times with different parameters
Title: Message Title Joe Ebmeier created an issue Jenkins / JENKINS-33178 Build pipeline displays incorrectly when triggering the same project multiple times with different parameters Issue Type: Bug Assignee: huybrechts Components: build-pipeline-plugin, parameterized-trigger-plugin Created: 26/Feb/16 1:39 PM Labels: plugin jenkins plugins Priority: Major Reporter: Joe Ebmeier OS: Ubuntu 14.04 (64-bit) openjdk version "1.8.0_72-internal" OpenJDK Runtime Environment (build 1.8.0_72-internal-b15) OpenJDK 64-Bit Server VM (build 25.72-b15, mixed mode) Jenkins ver. 1.642.1 Parameterized trigger plugin 2.30 Checkstyle plugin 3.44 I have a project which calls another project (using the parameterized trigger plugin) multiple times with different parameters (I am passing different version of php to use while running unit tests / checkstyle). "Block until the triggered projects finish their builds" is checked. When the build executes, the build pipeline plugin displays the same data for both builds. When the first downstream build is building, both pipeline items display the same info about the first build. Then when the second downstream build starts building, both pipeline items display info about the second build.
[JIRA] [core] (JENKINS-33177) Same Build number series for multiple projects
Title: Message Title Amit Bhardwaj created an issue Jenkins / JENKINS-33177 Same Build number series for multiple projects Issue Type: Task Assignee: Unassigned Components: core, versionnumber-plugin Created: 26/Feb/16 1:27 PM Labels: plugin versioning buildnumber Priority: Minor Reporter: Amit Bhardwaj Hi Group! I have a requirement where I have 2-3 branches from a common master (say A-dev, B-dev2.0, C-Qa) and I want to run Jenkins for each branch and check stability of my code and binaries. Currently I run Jenkins Project for 'master' branch only and with each build I get a iterative next number as my build number (which is default behavior). But now that I have multiple branches to build, I have to use Jenkins for all branches. I think I will need to create Jenkins Project for all branches but don't know 'HOW CAN I KEEP BUILD NUMBER SEQUENCE" as same. Please let me know how can I achieve this. Regards AB
[JIRA] [subversion-plugin] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Alexander Rudnev commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials Why the issue is closed? The fact that workaround exists doesn't make the bug solved, it just lowers the priority. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33176) Git clean() results in clean after, not before
Title: Message Title Christophe Vanlancker created an issue Jenkins / JENKINS-33176 Git clean() results in clean after, not before Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 26/Feb/16 1:22 PM Environment: Jenkins ver. 1.646 Job DSL 1.43 hudson.plugins.git.GitSCM git@2.4.2 Priority: Minor Reporter: Christophe Vanlancker The documentation on the API Viewer specifies that: clean(boolean clean = true) Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. Defaults to false. https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.helpers.scm.GitContext.clean The result of using clean() is that in the Job configuration, "Clean after checkout" is selected, instead of "before" Current outcome: clean() --> true Desired outcome (after manually adding the Clean Before option) clean() -->
[JIRA] [p4-plugin] (JENKINS-29598) p4 polling doesn't trigger workflow
Title: Message Title Rick King assigned an issue to David Schott Jenkins / JENKINS-29598 p4 polling doesn't trigger workflow Change By: Rick King Assignee: Rick King David Schott Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28237) p4-plugin does not provide accurate polling results in workflow job
Title: Message Title Rick King assigned an issue to Robby Pocase Jenkins / JENKINS-28237 p4-plugin does not provide accurate polling results in workflow job Change By: Rick King Assignee: Rick King Robby Pocase Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-29598) p4 polling doesn't trigger workflow
Title: Message Title Rick King resolved as Fixed This issue is now fixed and merged into master. Jenkins / JENKINS-29598 p4 polling doesn't trigger workflow Change By: Rick King Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
