[JIRA] [active-choices-plugin] (JENKINS-32965) Issues with active Choice pluggin
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-32965 Issues with active Choice pluggin Change By: Bruno P. Kinoshita Priority: Blocker Minor 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] [active-choices-plugin] (JENKINS-32965) Issues with active Choice pluggin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-32965 Re: Issues with active Choice pluggin This issue is probably related to a core issue. Likely an issue with the classpath (see http://stackoverflow.com/questions/11556404/jenkins-build-error-java-lang-classnotfoundexception-hudson-remoting-launcher for example). I've linked another issue from xUnit with a similar exception message. Praveesh Moorkoth, does the issue still happen? 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-timeout-plugin] (JENKINS-32968) BuildTimeOut plugin throws NullPointerException
Title: Message Title
ikedam commented on JENKINS-32968
Re: BuildTimeOut plugin throws NullPointerException
I can't reproduce the issue yet even with "19" for "Time-out variable".
Please let me know followings:
Versions of your Jenkins and build-timeout plugin
Attach config.xml of the project when the problem occurs
It is usually located at ${JENKINS_HOME}/jobs/(project name)/config.xml
What is displayed for "Timeout minutes" when you reopen the project configuration page.
The web browser you use
This sounds like a configuration issue, and might occur only with specific browsers.
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] [active-choices-plugin] (JENKINS-32965) Issues with active Choice pluggin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-32965 Re: Issues with active Choice pluggin I believe these two issues are related from looking at the exception thrown. 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] [active-choices-plugin] (JENKINS-33326) Programmatic changes to Reactive Reference value do not cascade
Title: Message Title
Bruno P. Kinoshita commented on JENKINS-33326
Re: Programmatic changes to Reactive Reference value do not cascade
Hi Ioannis!
I used an existing job in my development workspace to give it a try. Here's my test scenario:
1 job with 2 AC parameters (normal one returning array [1,2,3,4], and another one referencing this first one). Both multi select parameters.
When I click with my mouse, changing the options in parameter #1, the parameter #2 gets updated as expected
The ID of the parameter #1 is multiple_select_choice-parameter-5757281551183_
Doing the following in my JS console changes the parameter value: jQuery("#multiple_select_choice-parameter-5757281551183_").val('2')
The parameter #2 is not updated
But typing the following in the JS console triggers the update in parameter #2: jQuery("#multiple_select_choice-parameter-5757281551183_").trigger('change')
So I assume you can trigger the parameters changes programmatically too. Does that help? Is there any other way I can try to reproduce the issue? Maybe I missed something from your current scenario, if so feel free to update the issue with some example or screen shots and I'll give it another go.
Cheers Bruno
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [active-choices-plugin] (JENKINS-28764) Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Jenkins / JENKINS-28764 Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts Change By: Bruno P. Kinoshita Status: Resolved Closed 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] [active-choices-plugin] (JENKINS-31849) Horizontal parameters
Title: Message Title Bruno P. Kinoshita closed an issue as Won't Fix Jenkins / JENKINS-31849 Horizontal parameters Change By: Bruno P. Kinoshita Status: Resolved Closed 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] [active-choices-plugin] (JENKINS-32566) Render an AC Reactive reference as a functional Jenkins File Parameter
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Jenkins / JENKINS-32566 Render an AC Reactive reference as a functional Jenkins File Parameter Change By: Bruno P. Kinoshita Status: Resolved Closed 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] [active-choices-plugin] (JENKINS-32461) jenkinsProject variable is not available in Multi-configuration project
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Jenkins / JENKINS-32461 jenkinsProject variable is not available in Multi-configuration project Change By: Bruno P. Kinoshita Status: Resolved Closed 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] [active-choices-plugin] (JENKINS-33370) Changing dropdown via keyboard doesn't update reactive parameters
Title: Message Title Bruno P. Kinoshita closed an issue as Won't Fix Jenkins / JENKINS-33370 Changing dropdown via keyboard doesn't update reactive parameters Change By: Bruno P. Kinoshita Status: Resolved Closed 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] [active-choices-plugin] (JENKINS-33370) Changing dropdown via keyboard doesn't update reactive parameters
Title: Message Title Bruno P. Kinoshita resolved as Won't Fix Hi Dana! First of all, thanks for reporting the issue. It was successfully reproduced, and TL;DR, the fix was to simply change the script to bind to change+keyup. However, I found that by doing so, while testing with check boxes it wouldn't change the element selected, but the keyup (i.e. pressing any key while the check box is selected) would fire a call to update the elements. We could then: Implement some extra logic in the callback to check whether the value changed since the last action Or ignore that and let the extra calls happen Even though I'd like to add this feature, I think I wouldn't have enough time to write a proper good solution, with tests, and make sure that it works with no bad side effects. So am marking the ticket as Won't Fix simply for not having enough time to create the good solution (and not 100% sure it would work in all browsers and parameter types too [e.g. the custom HTML reference parameters]). In case you have a working solution for that, or any other suggestion, feel free to re-open this ticket or comment here. Jenkins / JENKINS-33370 Changing dropdown via keyboard doesn't update reactive parameters Change By: Bruno P. Kinoshita Status: Open Resolved Resolution: Won't Fix Add Comment
[JIRA] [active-choices-plugin] (JENKINS-33370) Changing dropdown via keyboard doesn't update reactive parameters
Title: Message Title Bruno P. Kinoshita stopped work on JENKINS-33370 Change By: Bruno P. Kinoshita Status: In Progress Open 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] [active-choices-plugin] (JENKINS-33370) Changing dropdown via keyboard doesn't update reactive parameters
Title: Message Title Bruno P. Kinoshita commented on JENKINS-33370 Re: Changing dropdown via keyboard doesn't update reactive parameters We are listening to the "change" event in the referenced parameter. But when you press keydown in a select, it doesn't fire a change event, only when you focus out. 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] [active-choices-plugin] (JENKINS-33370) Changing dropdown via keyboard doesn't update reactive parameters
Title: Message Title Bruno P. Kinoshita commented on JENKINS-33370 Re: Changing dropdown via keyboard doesn't update reactive parameters From http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-eventgroupings-htmlevents *change* The change event occurs when a control loses the input focus and its value has been modified since gaining focus. This event is valid for INPUT, SELECT, and TEXTAREA. element. Bubbles: Yes Cancelable: No Context Info: None 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] [active-choices-plugin] (JENKINS-33370) Changing dropdown via keyboard doesn't update reactive parameters
Title: Message Title Bruno P. Kinoshita commented on JENKINS-33370 Re: Changing dropdown via keyboard doesn't update reactive parameters Successfully reproduced on Firefox 45.0. Happens only with Single select elements. Multi select works as expected. 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] [active-choices-plugin] (JENKINS-33370) Changing dropdown via keyboard doesn't update reactive parameters
Title: Message Title Bruno P. Kinoshita started work on JENKINS-33370 Change By: Bruno P. Kinoshita Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-choices-plugin] (JENKINS-33473) Groovy script with default values when job is started by timer
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-33473 Groovy script with default values when job is started by timer Change By: Bruno P. Kinoshita Labels: epic 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] [active-choices-plugin] (JENKINS-33473) Groovy script with default values when job is started by timer
Title: Message Title Bruno P. Kinoshita commented on JENKINS-33473 Re: Groovy script with default values when job is started by timer Hi Mattias, Thanks for reporting this issue, and for including some Groovy example code to reproduce it. The script is evaluated, and the choices returned are: [ONE:selected, TWO:selected, TREE:selected, FOUR:selected] The :selected syntax if used for the UI. When the timer wakes up and prepares to call the job, the script is never evaluated - as normally it would be - since no JS was triggered. So there is not array here yet. Now that Jenkins is executing the job anyway and knows that we are using parameters. So it calls the hudson.model.ParameterDefinition#getDefaultParameterValue method * In hudson.model.ParameterDefinition#getDefaultParameterValue, we return the first element if the script returned any element, or an empty string (the job fails if we pass null). I believe the way that the plug-in is treating timer/remote/chained job executions isn't ideal yet. So I'm not sure how to fix your issue right now. Will cut a new release, but wanted to provide you some feedback. And as my memory is quite bad, this works as a note to myself, so that in the future when I try to think about a workaround for this issue (and for that one you linked here) I'll re-start from here Feel free to ping this issue should you have any suggestions on how to fix it, or any more information that you find may be useful. Cheers, Bruno Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [wildfly-deployer-plugin] (JENKINS-33504) FATAL: missing dependencies
Title: Message Title Graham Stewart created an issue Jenkins / JENKINS-33504 FATAL: missing dependencies Issue Type: Bug Assignee: Dan Dillingham Components: wildfly-deployer-plugin Created: 13/Mar/16 6:35 AM Environment: Jenkins 1.625.2, wildfly-deployer-plugin 1.0.1, installed on turnkey Linux debian 14.0 Priority: Major Reporter: Graham Stewart I installed this plugin using the Jenkins manage plugins section. My initial error was FATAL: Unable to initialize command context. because I had not installed wildfly-cli 8.2.1.Final This file was difficult find and also find the location for it to be installed. It would helpful if the instruction assisted this process. Eventually I found that the WEB-INF/lib dir is actually in two locations, one is in the /var/cache/jenkins/war dir and the others is in jenkins.war in /usr/share/jenkins. The .war must get expanded to /var/cache on regular basis so the files will need to be in both places. I then had succession of FATAL: org/wildfly/security/manager/WildFlySecurityManagerjava.lang.NoClassDefFoundError: Caused by: java.lang.ClassNotFoundException. for a missing class Every time I would find the required jar containing the missing class and install in the /var/cache and restart. Eventually I created a blank maven project with org.wildlfy wildlfy-cli
[JIRA] [wildfly-deployer-plugin] (JENKINS-33504) FATAL: missing dependencies
Title: Message Title Graham Stewart created an issue Jenkins / JENKINS-33504 FATAL: missing dependencies Issue Type: Bug Assignee: Dan Dillingham Components: wildfly-deployer-plugin Created: 13/Mar/16 6:35 AM Environment: Jenkins 1.625.2, wildfly-deployer-plugin 1.0.1, installed on turnkey Linux debian 14.0 Priority: Major Reporter: Graham Stewart I installed this plugin using the Jenkins manage plugins section. My initial error was FATAL: Unable to initialize command context. because I had not installed wildfly-cli 8.2.1.Final This file was difficult find and also find the location for it to be installed. It would helpful if the instruction assisted this process. Eventually I found that the WEB-INF/lib dir is actually in two locations, one is in the /var/cache/jenkins/war dir and the others is in jenkins.war in /usr/share/jenkins. The .war must get expanded to /var/cache on regular basis so the files will need to be in both places. I then had succession of FATAL: org/wildfly/security/manager/WildFlySecurityManagerjava.lang.NoClassDefFoundError: Caused by: java.lang.ClassNotFoundException. for a missing class Every time I would find the required jar containing the missing class and install in the /var/cache and restart. Eventually I created a blank maven project with org.wildlfy wildlfy-cli
[JIRA] [build-timeout-plugin] (JENKINS-32968) BuildTimeOut plugin throws NullPointerException
Title: Message Title Paul Poling edited a comment on JENKINS-32968 Re: BuildTimeOut plugin throws NullPointerException I encountered this after accidentally entering "19" for the "Time-out variable". Definitely would have appreciated a more helpful error than "FATAL: null" I've updated the Description with Steps to Reproduce for my case Thx 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-timeout-plugin] (JENKINS-32968) BuildTimeOut plugin throws NullPointerException
Title: Message Title
Paul Poling updated an issue
Jenkins / JENKINS-32968
BuildTimeOut plugin throws NullPointerException
Change By:
Paul Poling
*Steps to Reproduce*: [from ntulele]# Enable plugin for a job# Set the following:## Timeout strategy: Absolute## Timeout minutes: 3## *Time-out variable: 19*## Time-out actions:### Abort the build### Writing the build description (& enter some text)# Save/Apply and attempt to execute build# Note failure with stack trace per below# delete "19" from the Time-out variable text box# Save/Apply & re-attempt build --> PASS build-timeout-plugin 1.16 on Jenkins 1.647 is throwing the following exception Log excerpt:{code}FATAL: nulljava.lang.NullPointerException at hudson.plugins.build_timeout.BuildTimeOutStrategy.hasMacros(BuildTimeOutStrategy.java:112) at hudson.plugins.build_timeout.BuildTimeOutStrategy.expandAll(BuildTimeOutStrategy.java:108) at hudson.plugins.build_timeout.impl.AbsoluteTimeOutStrategy.getTimeOut(AbsoluteTimeOutStrategy.java:44) at hudson.plugins.build_timeout.BuildTimeoutWrapper$EnvironmentImpl.(BuildTimeoutWrapper.java:166) at hudson.plugins.build_timeout.BuildTimeoutWrapper.setUp(BuildTimeoutWrapper.java:211) 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){code}_from Maciej:_ It happens probably because Action field was not set. I would expect from the plugin a minimal message saying which field should not be null if it is about invalid configuration.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [build-timeout-plugin] (JENKINS-32968) BuildTimeOut plugin throws NullPointerException
Title: Message Title
Paul Poling updated an issue
Jenkins / JENKINS-32968
BuildTimeOut plugin throws NullPointerException
Change By:
Paul Poling
*Steps to Reproduce*: [from ntulele]# Enable plugin for a job# Set the following:## Timeout strategy: Absolute## Timeout minutes: 3## *Time-out variable: 19*## Time-out actions:### Abort the build ### Writing the build description (& enter some text)# Save/Apply and attempt to execute build# Note failure with stack trace per below# delete "19" from the Time - out variable text box# Save/Apply & re-attempt build --> PASSbuild- timeout-plugin 1.16 on Jenkins 1.647 is throwing the following exception Log excerpt:{code} FATAL: nulljava.lang.NullPointerException at hudson.plugins.build_timeout.BuildTimeOutStrategy.hasMacros(BuildTimeOutStrategy.java:112) at hudson.plugins.build_timeout.BuildTimeOutStrategy.expandAll(BuildTimeOutStrategy.java:108) at hudson.plugins.build_timeout.impl.AbsoluteTimeOutStrategy.getTimeOut(AbsoluteTimeOutStrategy.java:44) at hudson.plugins.build_timeout.BuildTimeoutWrapper$EnvironmentImpl.(BuildTimeoutWrapper.java:166) at hudson.plugins.build_timeout.BuildTimeoutWrapper.setUp(BuildTimeoutWrapper.java:211) 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) {code} _from It happens probably because Action field was not set. I would expect from the plugin a minimal message saying which field should not be null if it is about invalid configuration.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [build-timeout-plugin] (JENKINS-32968) BuildTimeOut plugin throws NullPointerException
Title: Message Title Paul Poling commented on JENKINS-32968 Re: BuildTimeOut plugin throws NullPointerException I encountered this after accidentally entering "19" for the "Time-out variable". Definitely would have appreciated a more helpful error than "FATAL: null" Thx 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] [multi-branch-project-plugin] (JENKINS-33503) 2-3 builds run in parallel after first commit
Title: Message Title mor lajb created an issue Jenkins / JENKINS-33503 2-3 builds run in parallel after first commit Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 13/Mar/16 5:57 AM Environment: plugin version 0.4.1 Jenkins 1.625.2 Priority: Major Reporter: mor lajb after upgrade to 0.4.1 ( previous was 0.3). when commit to a new branch the build trigger 3 times in parallel. the expected result is that only 1 build should trigger - and if I want to run the build in parallel I should mark it on the specific checkbox. Add Comment
[JIRA] [multi-branch-project-plugin] (JENKINS-33502) commit to a new branch trigger the build twice
Title: Message Title mor lajb created an issue Jenkins / JENKINS-33502 commit to a new branch trigger the build twice Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 13/Mar/16 5:54 AM Environment: multi branch plugin 0.3 ( try it on version 0.4.1). Jenkins 1.625.2 Priority: Major Reporter: mor lajb when commit to a new branch two different build were triggered. It appear only with large amount of branches ( more than 50) on smaller projects it works fine. the expected result should be that only 1 build should trigger. Add Comment
[JIRA] [gitlab-plugin] (JENKINS-33373) Rebuild open Merge Request
Title: Message Title Chris Denneen updated an issue Jenkins / JENKINS-33373 Rebuild open Merge Request Attaching screenshot of commits for Upstream and Fork Change By: Chris Denneen Attachment: Fork.png Attachment: Upstream.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] [gitlab-plugin] (JENKINS-33373) Rebuild open Merge Request
Title: Message Title Chris Denneen updated an issue Jenkins / JENKINS-33373 Rebuild open Merge Request Change By: Chris Denneen Attachment: Screen Shot 2016-03-12 at 7.46.26 PM.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] [gitlab-plugin] (JENKINS-33373) Rebuild open Merge Request
Title: Message Title Chris Denneen updated an issue Jenkins / JENKINS-33373 Rebuild open Merge Request Change By: Chris Denneen Attachment: Screen Shot 2016-03-12 at 7.46.38 PM.png Attachment: Screen Shot 2016-03-12 at 7.46.26 PM.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] [gitlab-plugin] (JENKINS-33373) Rebuild open Merge Request
Title: Message Title Chris Denneen updated an issue Jenkins / JENKINS-33373 Rebuild open Merge Request Change By: Chris Denneen Attachment: Screen Shot 2016-03-12 at 7.46.38 PM.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] [gitlab-plugin] (JENKINS-33373) Rebuild open Merge Request
Title: Message Title Chris Denneen commented on JENKINS-33373 Re: Rebuild open Merge Request Only if the source/target are the same repository, not fork. Currently the only way around this is to add this web hook to every fork (but this isn't reasonable). In the https://github.com/timols/jenkins-gitlab-merge-request-builder-plugin Gitlab Merge Request plugin this behavior works. If you notice when you commit to the fork the open MR shows the updated commits which would in theory trigger the build again. Also currently the fork commits, while tested during the merge request, don't get build status updates in Gitlab. After the merge request is accepted the "Merge" is then tested but those commits in the merge themselves don't have any build status on source or target repositories. 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-33466) Current master branch fail to build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33466 Re: Current master branch fail to build Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/DslEnvironmentImplSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/5d924941836f4486aabbdbccb109fd1d3e0f3331 Log: Merge pull request #784 from daspilker/ JENKINS-33466 JENKINS-33466 removed TestAbstractExtensibleContext Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/0f6e0ca8054c...5d924941836f 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-33466) Current master branch fail to build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33466 Re: Current master branch fail to build Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/DslEnvironmentImplSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/22ea15de1b8c5b8b4342ace5829dc639bd48ac98 Log: removed TestAbstractExtensibleContext to avoid compile time problems [FIXED JENKINS-33466] 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-33466) Current master branch fail to build
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-33466 Current master branch fail to build Change By: SCM/JIRA link daemon Status: Reopened 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] [job-dsl-plugin] (JENKINS-33466) Current master branch fail to build
Title: Message Title Daniel Spilker reopened an issue meh, another CI build failed Jenkins / JENKINS-33466 Current master branch fail to build Change By: Daniel Spilker Resolution: Cannot Reproduce Status: Resolved Reopened 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-plugin] (JENKINS-33501) Exception when attempting to use GitHub credentials
Title: Message Title
Evan Nemerson created an issue
Jenkins / JENKINS-33501
Exception when attempting to use GitHub credentials
Issue Type:
Bug
Assignee:
Kirill Merkushev
Components:
github-plugin
Created:
12/Mar/16 9:21 PM
Environment:
Fedora 23 POWER8 LE, openjdk 1.8.0-72, guava 18.0, jenkins 1.625.3
Priority:
Major
Reporter:
Evan Nemerson
I'm trying to use the github plugin, but whenever it tries to use the github credentials, I get this:
{{javax.servlet.ServletException: java.lang.NoSuchMethodError: com.google.common.hash.Hasher.putString(Ljava/lang/CharSequence;)Lcom/google/common/hash/Hasher; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) 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:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496) at
[JIRA] [job-dsl-plugin] (JENKINS-33466) Current master branch fail to build
Title: Message Title Daniel Spilker resolved as Cannot Reproduce Seems to be a CI glitch. Jenkins / JENKINS-33466 Current master branch fail to build Change By: Daniel Spilker Status: Open Resolved Resolution: Cannot Reproduce 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-33456) durable-task 1.8 breaks workflow bat steps
Title: Message Title
Aleksei Vakulenko edited a comment on JENKINS-33456
Re: durable-task 1.8 breaks workflow bat steps
I think problem not only this plugin, but in some plugin of Pipeline v 1.15.Version of Windows - 7 64 bit SP1.In example program 1c.exe replaced 7z.exe*simple script on python:* {code:java} # coding: utf8import subprocessimport osimport timedef main(): call_string = 'C:\\Program Files\\7-Zip\\7z.exe t ' + os.getcwd() + '\\Empty.7z' print(call_string) subprocess.call(call_string) time.sleep(10) if __name__ == '__main__': main() {code} *workflow script for test:*node{wrap([$class: 'TimestamperBuildWrapper']) { stash includes: 'Python.py, Empty.7z', name: 'zip' timeout(10) { bat 'python python.py' } }}parallel Branch1: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } },Branch2: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } } failFast: false*workflow log:*{code:java}[Pipeline] Allocate node : StartRunning on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] node {[Pipeline] General Build Wrapper : Start[Pipeline] wrap {[Pipeline] stash19:31:21 Stashed 1 file(s)[Pipeline] Enforce time limit : Start[Pipeline] timeout {[Pipeline] bat19:31:21 [UT_Develop] Running batch script19:31:21 19:31:21 C:\Jenkins\workspace\UT_Develop>python python.py 19:31:21 19:31:21 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:31:21 19:31:21 19:31:21 Error:19:31:21 cannot find archive19:32:28 C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] Execute in parallel : Start[Pipeline] [Branch1] parallel { (Branch: Branch1)[Pipeline] [Branch2] parallel { (Branch: Branch2)[Pipeline] [Branch1] Allocate node : Start[Branch1] Running on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] [Branch2] Allocate node : Start[Branch2] Running on мастер in C:\Jenkins\workspace\UT_Develop@2[Pipeline] [Branch1] node {[Pipeline] [Branch2] node {[Pipeline] [Branch1] General Build Wrapper : Start[Pipeline] [Branch1] wrap {[Pipeline] [Branch2] General Build Wrapper : Start[Pipeline] [Branch2] wrap {[Pipeline] [Branch1] unstash[Pipeline] [Branch2] unstash[Pipeline] [Branch1] Enforce time limit : Start[Pipeline] [Branch1] timeout {[Pipeline] [Branch2] Enforce time limit : Start[Pipeline] [Branch2] timeout {[Pipeline] [Branch1] bat19:32:29 [Branch1] [UT_Develop] Running batch script[Pipeline] [Branch2] bat19:32:29 [Branch1] 19:32:29 [Branch1] C:\Jenkins\workspace\UT_Develop>python python.py 19:32:29 [Branch1] 19:32:29 [Branch1] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch1] 19:32:29 [Branch1] 19:32:29 [Branch1] Error:19:32:29 [Branch1] cannot find archive19:32:29 [Branch2] [UT_Develop@2] Running batch script19:32:29 [Branch2] 19:32:29 [Branch2] C:\Jenkins\workspace\UT_Develop@2>python python.py 19:32:29 [Branch2] 19:32:29 [Branch2] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch2] 19:32:29 [Branch2] 19:32:29 [Branch2] Error:19:32:29 [Branch2] cannot find archive19:33:37 [Branch1] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z19:33:37 [Branch2] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop@2\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] } //parallel{code}and _"little spinning icon"_sorry my text decoration
[JIRA] [durable-task-plugin] (JENKINS-33456) durable-task 1.8 breaks workflow bat steps
Title: Message Title
Aleksei Vakulenko edited a comment on JENKINS-33456
Re: durable-task 1.8 breaks workflow bat steps
I think problem not only this plugin, but in some plugin of Pipeline v 1.15.Version of Windows - 7 64 bit SP1.In example program 1c.exe replaced 7z.exe*simple script on python:*{code:java}# coding: utf8import subprocessimport osimport timedef main(): call_string = 'C:\\Program Files\\7-Zip\\7z.exe t ' + os.getcwd() + '\\Empty.7z' print(call_string) subprocess.call(call_string) time.sleep(10) if __name__ == '__main__': main(){code}*workflow script for test:* {code:java} node{wrap([$class: 'TimestamperBuildWrapper']) { stash includes: 'Python.py, Empty.7z', name: 'zip' timeout(10) { bat 'python python.py' } }}parallel Branch1: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } },Branch2: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } } failFast: false {code} *workflow log:*{code:java}[Pipeline] Allocate node : StartRunning on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] node {[Pipeline] General Build Wrapper : Start[Pipeline] wrap {[Pipeline] stash19:31:21 Stashed 1 file(s)[Pipeline] Enforce time limit : Start[Pipeline] timeout {[Pipeline] bat19:31:21 [UT_Develop] Running batch script19:31:21 19:31:21 C:\Jenkins\workspace\UT_Develop>python python.py 19:31:21 19:31:21 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:31:21 19:31:21 19:31:21 Error:19:31:21 cannot find archive19:32:28 C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] Execute in parallel : Start[Pipeline] [Branch1] parallel { (Branch: Branch1)[Pipeline] [Branch2] parallel { (Branch: Branch2)[Pipeline] [Branch1] Allocate node : Start[Branch1] Running on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] [Branch2] Allocate node : Start[Branch2] Running on мастер in C:\Jenkins\workspace\UT_Develop@2[Pipeline] [Branch1] node {[Pipeline] [Branch2] node {[Pipeline] [Branch1] General Build Wrapper : Start[Pipeline] [Branch1] wrap {[Pipeline] [Branch2] General Build Wrapper : Start[Pipeline] [Branch2] wrap {[Pipeline] [Branch1] unstash[Pipeline] [Branch2] unstash[Pipeline] [Branch1] Enforce time limit : Start[Pipeline] [Branch1] timeout {[Pipeline] [Branch2] Enforce time limit : Start[Pipeline] [Branch2] timeout {[Pipeline] [Branch1] bat19:32:29 [Branch1] [UT_Develop] Running batch script[Pipeline] [Branch2] bat19:32:29 [Branch1] 19:32:29 [Branch1] C:\Jenkins\workspace\UT_Develop>python python.py 19:32:29 [Branch1] 19:32:29 [Branch1] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch1] 19:32:29 [Branch1] 19:32:29 [Branch1] Error:19:32:29 [Branch1] cannot find archive19:32:29 [Branch2] [UT_Develop@2] Running batch script19:32:29 [Branch2] 19:32:29 [Branch2] C:\Jenkins\workspace\UT_Develop@2>python python.py 19:32:29 [Branch2] 19:32:29 [Branch2] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch2] 19:32:29 [Branch2] 19:32:29 [Branch2] Error:19:32:29 [Branch2] cannot find archive19:33:37 [Branch1] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z19:33:37 [Branch2] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop@2\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] } //parallel{code}and _"little spinning icon"_sorry my text decoration
[JIRA] [durable-task-plugin] (JENKINS-33456) durable-task 1.8 breaks workflow bat steps
Title: Message Title
Aleksei Vakulenko edited a comment on JENKINS-33456
Re: durable-task 1.8 breaks workflow bat steps
I think problem not only this plugin, but in some plugin of Pipeline v 1.15.Version of Windows - 7 64 bit SP1.In example program 1c.exe replaced 7z.exe*simple script on python:*# coding: utf8import subprocessimport osimport timedef main(): call_string = 'C:\\Program Files\\7-Zip\\7z.exe t ' + os.getcwd() + '\\Empty.7z' print(call_string) subprocess.call(call_string) time.sleep(10) if __name__ == '__main__': main()*workflow script for test:*node{wrap([$class: 'TimestamperBuildWrapper']) { stash includes: 'Python.py, Empty.7z', name: 'zip' timeout(10) { bat 'python python.py' } }}parallel Branch1: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } },Branch2: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } } failFast: false*workflow log:* {code:java} [Pipeline] Allocate node : StartRunning on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] node {[Pipeline] General Build Wrapper : Start[Pipeline] wrap {[Pipeline] stash19:31:21 Stashed 1 file(s)[Pipeline] Enforce time limit : Start[Pipeline] timeout {[Pipeline] bat19:31:21 [UT_Develop] Running batch script19:31:21 19:31:21 C:\Jenkins\workspace\UT_Develop>python python.py 19:31:21 19:31:21 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:31:21 19:31:21 19:31:21 Error:19:31:21 cannot find archive19:32:28 C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] Execute in parallel : Start[Pipeline] [Branch1] parallel { (Branch: Branch1)[Pipeline] [Branch2] parallel { (Branch: Branch2)[Pipeline] [Branch1] Allocate node : Start[Branch1] Running on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] [Branch2] Allocate node : Start[Branch2] Running on мастер in C:\Jenkins\workspace\UT_Develop@2[Pipeline] [Branch1] node {[Pipeline] [Branch2] node {[Pipeline] [Branch1] General Build Wrapper : Start[Pipeline] [Branch1] wrap {[Pipeline] [Branch2] General Build Wrapper : Start[Pipeline] [Branch2] wrap {[Pipeline] [Branch1] unstash[Pipeline] [Branch2] unstash[Pipeline] [Branch1] Enforce time limit : Start[Pipeline] [Branch1] timeout {[Pipeline] [Branch2] Enforce time limit : Start[Pipeline] [Branch2] timeout {[Pipeline] [Branch1] bat19:32:29 [Branch1] [UT_Develop] Running batch script[Pipeline] [Branch2] bat19:32:29 [Branch1] 19:32:29 [Branch1] C:\Jenkins\workspace\UT_Develop>python python.py 19:32:29 [Branch1] 19:32:29 [Branch1] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch1] 19:32:29 [Branch1] 19:32:29 [Branch1] Error:19:32:29 [Branch1] cannot find archive19:32:29 [Branch2] [UT_Develop@2] Running batch script19:32:29 [Branch2] 19:32:29 [Branch2] C:\Jenkins\workspace\UT_Develop@2>python python.py 19:32:29 [Branch2] 19:32:29 [Branch2] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch2] 19:32:29 [Branch2] 19:32:29 [Branch2] Error:19:32:29 [Branch2] cannot find archive19:33:37 [Branch1] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z19:33:37 [Branch2] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop@2\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] } //parallel {code} and _"little spinning icon"_sorry my text decoration
[JIRA] [ci-game-plugin] (JENKINS-23939) CI Game doesn't count points for Maven Project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-23939 Re: CI Game doesn't count points for Maven Project Code changed in jenkins User: Lewis Vail Path: src/main/java/hudson/plugins/cigame/rules/plugins/findbugs/AbstractFindBugsWarningsRule.java http://jenkins-ci.org/commit/ci-game-plugin/a4b049727d4ca853567fefb4614f703380983469 Log: JENKINS-23939 Updated AbstractFindBugsWarningsRule.evaluate(AbstractBuild, AbstractBuild) to evaluate FindBugsMavenResultActions if no FindBugsResultActions are found for the current build. 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] [ci-game-plugin] (JENKINS-23939) CI Game doesn't count points for Maven Project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-23939 Re: CI Game doesn't count points for Maven Project Code changed in jenkins User: Lewis Vail Path: src/test/java/hudson/plugins/cigame/rules/plugins/findbugs/FixedFindBugsWarningsRuleTest.java src/test/java/hudson/plugins/cigame/rules/plugins/findbugs/NewFindBugsWarningsRuleTest.java http://jenkins-ci.org/commit/ci-game-plugin/acfc2891917ab0cdcccfc7e968f32bfdfb0515d4 Log: JENKINS-23939 Updated FindBugs and unit tests to verify changes to support maven builds. 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] [ci-game-plugin] (JENKINS-23939) CI Game doesn't count points for Maven Project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-23939 Re: CI Game doesn't count points for Maven Project Code changed in jenkins User: Lewis Vail Path: src/main/java/hudson/plugins/cigame/rules/plugins/findbugs/AbstractFindBugsWarningsRule.java http://jenkins-ci.org/commit/ci-game-plugin/7ea7054df856cf00a5225f8632f0e097afec4924 Log: JENKINS-23939 Fixed regression issue where removing a maven module didn't mark it's findbugs issues as 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] [durable-task-plugin] (JENKINS-33456) durable-task 1.8 breaks workflow bat steps
Title: Message Title
Aleksei Vakulenko edited a comment on JENKINS-33456
Re: durable-task 1.8 breaks workflow bat steps
I think problem not only this plugin, but in some plugin of Pipeline v 11 1 . 5 15 .Version of Windows - 7 64 bit SP1.In example program 1c.exe replaced 7z.exe*simple script on python:*# coding: utf8import subprocessimport osimport timedef main(): call_string = 'C:\\Program Files\\7-Zip\\7z.exe t ' + os.getcwd() + '\\Empty.7z' print(call_string) subprocess.call(call_string) time.sleep(10) if __name__ == '__main__': main()*workflow script for test:*node{wrap([$class: 'TimestamperBuildWrapper']) { stash includes: 'Python.py, Empty.7z', name: 'zip' timeout(10) { bat 'python python.py' } }}parallel Branch1: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } },Branch2: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } } failFast: false*workflow log:*[Pipeline] Allocate node : StartRunning on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] node {[Pipeline] General Build Wrapper : Start[Pipeline] wrap {[Pipeline] stash19:31:21 Stashed 1 file(s)[Pipeline] Enforce time limit : Start[Pipeline] timeout {[Pipeline] bat19:31:21 [UT_Develop] Running batch script19:31:21 19:31:21 C:\Jenkins\workspace\UT_Develop>python python.py 19:31:21 19:31:21 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:31:21 19:31:21 19:31:21 Error:19:31:21 cannot find archive19:32:28 C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] Execute in parallel : Start[Pipeline] [Branch1] parallel { (Branch: Branch1)[Pipeline] [Branch2] parallel { (Branch: Branch2)[Pipeline] [Branch1] Allocate node : Start[Branch1] Running on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] [Branch2] Allocate node : Start[Branch2] Running on мастер in C:\Jenkins\workspace\UT_Develop@2[Pipeline] [Branch1] node {[Pipeline] [Branch2] node {[Pipeline] [Branch1] General Build Wrapper : Start[Pipeline] [Branch1] wrap {[Pipeline] [Branch2] General Build Wrapper : Start[Pipeline] [Branch2] wrap {[Pipeline] [Branch1] unstash[Pipeline] [Branch2] unstash[Pipeline] [Branch1] Enforce time limit : Start[Pipeline] [Branch1] timeout {[Pipeline] [Branch2] Enforce time limit : Start[Pipeline] [Branch2] timeout {[Pipeline] [Branch1] bat19:32:29 [Branch1] [UT_Develop] Running batch script[Pipeline] [Branch2] bat19:32:29 [Branch1] 19:32:29 [Branch1] C:\Jenkins\workspace\UT_Develop>python python.py 19:32:29 [Branch1] 19:32:29 [Branch1] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch1] 19:32:29 [Branch1] 19:32:29 [Branch1] Error:19:32:29 [Branch1] cannot find archive19:32:29 [Branch2] [UT_Develop@2] Running batch script19:32:29 [Branch2] 19:32:29 [Branch2] C:\Jenkins\workspace\UT_Develop@2>python python.py 19:32:29 [Branch2] 19:32:29 [Branch2] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch2] 19:32:29 [Branch2] 19:32:29 [Branch2] Error:19:32:29 [Branch2] cannot find archive19:33:37 [Branch1] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z19:33:37 [Branch2] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop@2\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] } //paralleland _"little spinning icon"_sorry my text decoration
[JIRA] [durable-task-plugin] (JENKINS-33456) durable-task 1.8 breaks workflow bat steps
Title: Message Title
Aleksei Vakulenko edited a comment on JENKINS-33456
Re: durable-task 1.8 breaks workflow bat steps
I think problem not only this plugin, but in some plugin of Pipeline v 11.5.Version of Windows - 7 64 bit SP1.In example program 1c.exe replaced 7z.exe*simple script on python:*# coding: utf8import subprocessimport osimport timedef main(): call_string = 'C:\\Program Files\\7-Zip\\7z.exe t ' + os.getcwd() + '\\Empty.7z' print(call_string) subprocess.call(call_string) time.sleep(10) if __name__ == '__main__': main()*workflow script for test:*node{wrap([$class: 'TimestamperBuildWrapper']) { stash includes: 'Python.py, Empty.7z', name: 'zip' timeout(10) { bat 'python python.py' } }}parallel Branch1: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } },Branch2: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } } failFast: false*workflow log:*[Pipeline] Allocate node : StartRunning on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] node {[Pipeline] General Build Wrapper : Start[Pipeline] wrap {[Pipeline] stash19:31:21 Stashed 1 file(s)[Pipeline] Enforce time limit : Start[Pipeline] timeout {[Pipeline] bat19:31:21 [UT_Develop] Running batch script19:31:21 19:31:21 C:\Jenkins\workspace\UT_Develop>python python.py 19:31:21 19:31:21 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:31:21 19:31:21 19:31:21 Error:19:31:21 cannot find archive19:32:28 C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] Execute in parallel : Start[Pipeline] [Branch1] parallel { (Branch: Branch1)[Pipeline] [Branch2] parallel { (Branch: Branch2)[Pipeline] [Branch1] Allocate node : Start[Branch1] Running on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] [Branch2] Allocate node : Start[Branch2] Running on мастер in C:\Jenkins\workspace\UT_Develop@2[Pipeline] [Branch1] node {[Pipeline] [Branch2] node {[Pipeline] [Branch1] General Build Wrapper : Start[Pipeline] [Branch1] wrap {[Pipeline] [Branch2] General Build Wrapper : Start[Pipeline] [Branch2] wrap {[Pipeline] [Branch1] unstash[Pipeline] [Branch2] unstash[Pipeline] [Branch1] Enforce time limit : Start[Pipeline] [Branch1] timeout {[Pipeline] [Branch2] Enforce time limit : Start[Pipeline] [Branch2] timeout {[Pipeline] [Branch1] bat19:32:29 [Branch1] [UT_Develop] Running batch script[Pipeline] [Branch2] bat19:32:29 [Branch1] 19:32:29 [Branch1] C:\Jenkins\workspace\UT_Develop>python python.py 19:32:29 [Branch1] 19:32:29 [Branch1] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch1] 19:32:29 [Branch1] 19:32:29 [Branch1] Error:19:32:29 [Branch1] cannot find archive19:32:29 [Branch2] [UT_Develop@2] Running batch script19:32:29 [Branch2] 19:32:29 [Branch2] C:\Jenkins\workspace\UT_Develop@2>python python.py 19:32:29 [Branch2] 19:32:29 [Branch2] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch2] 19:32:29 [Branch2] 19:32:29 [Branch2] Error:19:32:29 [Branch2] cannot find archive19:33:37 [Branch1] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z19:33:37 [Branch2] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop@2\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] } //paralleland _"little spinning icon"_sorry my text decoration
[JIRA] [durable-task-plugin] (JENKINS-33456) durable-task 1.8 breaks workflow bat steps
Title: Message Title
Aleksei Vakulenko edited a comment on JENKINS-33456
Re: durable-task 1.8 breaks workflow bat steps
I think problem not only this plugin, but in some plugin of Pipeline v 11.5.Version of Windows - 7 64 bit SP1. In example program 1c.exe 7z.exe *simple script on python:*# coding: utf8import subprocessimport osimport timedef main(): call_string = 'C:\\Program Files\\7-Zip\\7z.exe t ' + os.getcwd() + '\\Empty.7z' print(call_string) subprocess.call(call_string) time.sleep(10) if __name__ == '__main__': main()*workflow script for test:*node{wrap([$class: 'TimestamperBuildWrapper']) { stash includes: 'Python.py, Empty.7z', name: 'zip' timeout(10) { bat 'python python.py' } }}parallel Branch1: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } },Branch2: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } } failFast: false*workflow log:*[Pipeline] Allocate node : StartRunning on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] node {[Pipeline] General Build Wrapper : Start[Pipeline] wrap {[Pipeline] stash19:31:21 Stashed 1 file(s)[Pipeline] Enforce time limit : Start[Pipeline] timeout {[Pipeline] bat19:31:21 [UT_Develop] Running batch script19:31:21 19:31:21 C:\Jenkins\workspace\UT_Develop>python python.py 19:31:21 19:31:21 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:31:21 19:31:21 19:31:21 Error:19:31:21 cannot find archive19:32:28 C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] Execute in parallel : Start[Pipeline] [Branch1] parallel { (Branch: Branch1)[Pipeline] [Branch2] parallel { (Branch: Branch2)[Pipeline] [Branch1] Allocate node : Start[Branch1] Running on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] [Branch2] Allocate node : Start[Branch2] Running on мастер in C:\Jenkins\workspace\UT_Develop@2[Pipeline] [Branch1] node {[Pipeline] [Branch2] node {[Pipeline] [Branch1] General Build Wrapper : Start[Pipeline] [Branch1] wrap {[Pipeline] [Branch2] General Build Wrapper : Start[Pipeline] [Branch2] wrap {[Pipeline] [Branch1] unstash[Pipeline] [Branch2] unstash[Pipeline] [Branch1] Enforce time limit : Start[Pipeline] [Branch1] timeout {[Pipeline] [Branch2] Enforce time limit : Start[Pipeline] [Branch2] timeout {[Pipeline] [Branch1] bat19:32:29 [Branch1] [UT_Develop] Running batch script[Pipeline] [Branch2] bat19:32:29 [Branch1] 19:32:29 [Branch1] C:\Jenkins\workspace\UT_Develop>python python.py 19:32:29 [Branch1] 19:32:29 [Branch1] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch1] 19:32:29 [Branch1] 19:32:29 [Branch1] Error:19:32:29 [Branch1] cannot find archive19:32:29 [Branch2] [UT_Develop@2] Running batch script19:32:29 [Branch2] 19:32:29 [Branch2] C:\Jenkins\workspace\UT_Develop@2>python python.py 19:32:29 [Branch2] 19:32:29 [Branch2] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch2] 19:32:29 [Branch2] 19:32:29 [Branch2] Error:19:32:29 [Branch2] cannot find archive19:33:37 [Branch1] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z19:33:37 [Branch2] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop@2\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] } //paralleland _"little spinning icon"_sorry my text decoration
[JIRA] [durable-task-plugin] (JENKINS-33456) durable-task 1.8 breaks workflow bat steps
Title: Message Title
Aleksei Vakulenko edited a comment on JENKINS-33456
Re: durable-task 1.8 breaks workflow bat steps
I think problem not only this plugin, but in some plugin of Pipeline v 11.5.Version of Windows - 7 64 bit SP1. * simple script on python: * # coding: utf8import subprocessimport osimport timedef main(): call_string = 'C:\\Program Files\\7-Zip\\7z.exe t ' + os.getcwd() + '\\Empty.7z' print(call_string) subprocess.call(call_string) time.sleep(10) if __name__ == '__main__': main() * workflow script for test: * node{wrap([$class: 'TimestamperBuildWrapper']) { stash includes: 'Python.py, Empty.7z', name: 'zip' timeout(10) { bat 'python python.py' } }}parallel Branch1: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } },Branch2: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } } failFast: false * workflow log: * [Pipeline] Allocate node : StartRunning on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] node {[Pipeline] General Build Wrapper : Start[Pipeline] wrap {[Pipeline] stash19:31:21 Stashed 1 file(s)[Pipeline] Enforce time limit : Start[Pipeline] timeout {[Pipeline] bat19:31:21 [UT_Develop] Running batch script19:31:21 19:31:21 C:\Jenkins\workspace\UT_Develop>python python.py 19:31:21 19:31:21 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:31:21 19:31:21 19:31:21 Error:19:31:21 cannot find archive19:32:28 C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] Execute in parallel : Start[Pipeline] [Branch1] parallel { (Branch: Branch1)[Pipeline] [Branch2] parallel { (Branch: Branch2)[Pipeline] [Branch1] Allocate node : Start[Branch1] Running on мастер in C:\Jenkins\workspace\UT_Develop[Pipeline] [Branch2] Allocate node : Start[Branch2] Running on мастер in C:\Jenkins\workspace\UT_Develop@2[Pipeline] [Branch1] node {[Pipeline] [Branch2] node {[Pipeline] [Branch1] General Build Wrapper : Start[Pipeline] [Branch1] wrap {[Pipeline] [Branch2] General Build Wrapper : Start[Pipeline] [Branch2] wrap {[Pipeline] [Branch1] unstash[Pipeline] [Branch2] unstash[Pipeline] [Branch1] Enforce time limit : Start[Pipeline] [Branch1] timeout {[Pipeline] [Branch2] Enforce time limit : Start[Pipeline] [Branch2] timeout {[Pipeline] [Branch1] bat19:32:29 [Branch1] [UT_Develop] Running batch script[Pipeline] [Branch2] bat19:32:29 [Branch1] 19:32:29 [Branch1] C:\Jenkins\workspace\UT_Develop>python python.py 19:32:29 [Branch1] 19:32:29 [Branch1] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch1] 19:32:29 [Branch1] 19:32:29 [Branch1] Error:19:32:29 [Branch1] cannot find archive19:32:29 [Branch2] [UT_Develop@2] Running batch script19:32:29 [Branch2] 19:32:29 [Branch2] C:\Jenkins\workspace\UT_Develop@2>python python.py 19:32:29 [Branch2] 19:32:29 [Branch2] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-1819:32:29 [Branch2] 19:32:29 [Branch2] 19:32:29 [Branch2] Error:19:32:29 [Branch2] cannot find archive19:33:37 [Branch1] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z19:33:37 [Branch2] C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop@2\Empty.7z[Pipeline] } //timeout[Pipeline] Enforce time limit : End[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] } //paralleland _ "little spinning icon" _sorry my text decoration
[JIRA] [durable-task-plugin] (JENKINS-33456) durable-task 1.8 breaks workflow bat steps
Title: Message Title
Aleksei Vakulenko commented on JENKINS-33456
Re: durable-task 1.8 breaks workflow bat steps
I think problem not only this plugin, but in some plugin of Pipeline v 11.5. Version of Windows - 7 64 bit SP1. simple script on python:
coding: utf8 import subprocess import os import time
def main(): call_string = 'C:Program Files\\7-Zip7z.exe t ' + os.getcwd() + 'Empty.7z' print(call_string) subprocess.call(call_string) time.sleep(10)
if _name_ == '_main_': main()
workflow script for test:
node{ wrap([$class: 'TimestamperBuildWrapper']) { stash includes: 'Python.py, Empty.7z', name: 'zip' timeout(10) { bat 'python python.py' }
} }
parallel Branch1: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' } } } },Branch2: { node { wrap([$class: 'TimestamperBuildWrapper']) { unstash 'zip' timeout(10) { bat 'python python.py' }
} } } failFast: false
workflow log:
[Pipeline] Allocate node : Start Running on мастер in C:\Jenkins\workspace\UT_Develop [Pipeline] node { [Pipeline] General Build Wrapper : Start [Pipeline] wrap { [Pipeline] stash 19:31:21 Stashed 1 file(s) [Pipeline] Enforce time limit : Start [Pipeline] timeout { [Pipeline] bat 19:31:21 [UT_Develop] Running batch script 19:31:21 19:31:21 C:\Jenkins\workspace\UT_Develop>python python.py 19:31:21 19:31:21 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18 19:31:21 19:31:21 19:31:21 Error: 19:31:21 cannot find archive 19:32:28 C:\Program Files\7-Zip\7z.exe t C:\Jenkins\workspace\UT_Develop\Empty.7z [Pipeline] }
//timeout [Pipeline] Enforce time limit : End [Pipeline] } //wrap [Pipeline] General Build Wrapper : End [Pipeline] } //node [Pipeline] Allocate node : End [Pipeline] Execute in parallel : Start [Pipeline] [Branch1] parallel { (Branch: Branch1) [Pipeline] [Branch2] parallel { (Branch: Branch2) [Pipeline] [Branch1] Allocate node : Start [Branch1] Running on мастер in C:\Jenkins\workspace\UT_Develop [Pipeline] [Branch2] Allocate node : Start [Branch2] Running on мастер in C:\Jenkins\workspace\UT_Develop@2 [Pipeline] [Branch1] node { [Pipeline] [Branch2] node { [Pipeline] [Branch1] General Build Wrapper : Start [Pipeline] [Branch1] wrap { [Pipeline] [Branch2] General Build Wrapper : Start [Pipeline] [Branch2] wrap { [Pipeline] [Branch1] unstash [Pipeline] [Branch2] unstash [Pipeline] [Branch1] Enforce time limit : Start [Pipeline] [Branch1] timeout { [Pipeline] [Branch2] Enforce time limit : Start [Pipeline] [Branch2] timeout { [Pipeline] [Branch1] bat 19:32:29 [Branch1] [UT_Develop] Running batch script [Pipeline] [Branch2] bat 19:32:29 [Branch1] 19:32:29 [Branch1] C:\Jenkins\workspace\UT_Develop>python python.py 19:32:29 [Branch1] 19:32:29 [Branch1] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18 19:32:29 [Branch1] 19:32:29 [Branch1] 19:32:29 [Branch1] Error: 19:32:29 [Branch1] cannot find archive 19:32:29 [Branch2] [UT_Develop@2] Running batch script 19:32:29 [Branch2] 19:32:29 [Branch2] C:\Jenkins\workspace\UT_Develop@2>python python.py 19:32:29 [Branch2] 19:32:29 [Branch2] 7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18 19:32:29 [Branch2] 19:32:29 [Branch2] 19:32:29
[JIRA] [mask-passwords-plugin] (JENKINS-33500) Masked passwords are shown for inheritance project
Title: Message Title Mark M updated an issue Jenkins / JENKINS-33500 Masked passwords are shown for inheritance project Change By: Mark M Masked Passwords are exposed from the _View/Download full build flow_ page.Steps to reproduce:Go to _Manage Jenkins_ --> _Configure System_Under _Mask Passwords - Global name/password pairs_ section:Add name/password pair:Name: SOME_PWDPassword: IShouldBeMasked Click _Save_Go to _Manage Jenkins_ --> _Configure Global Security_For _Markup Formatter_, select _Raw HTML_Click _Save_Go to _New Item_Item name: SomeProjectSelect _Inheritance Project_Click _OK_On the Configuration screen, under _Build Environment_ section, check _Mask passwords_Add name/password pair:Name: SOME_PWD2Password: IShouldAlsoBeMaskedClick _Save_Add a short description in the text field of the dialog, then click _OK_Click _Build Now_Select the specific build under the _Build History_ sectionClick _View/Download full build flow_Under the _All build parameters_ section, the password values are shown.Also with the Download option the password values are exposed in the shell script export. 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] [mask-passwords-plugin] (JENKINS-33500) Masked passwords are shown for inheritance project
Title: Message Title Mark M updated an issue Jenkins / JENKINS-33500 Masked passwords are shown for inheritance project Change By: Mark M Masked Passwords are exposed from the _View/Download full build flow_ page.Steps to reproduce:Go to _Manage Jenkins_ --> _Configure System_Under _Mask Passwords - Global name/password pairs_ section:Add name/password pair: - Name: SOME_PWD - Password: IShouldBeMasked Click _Save_Go to _Manage Jenkins_ --> _Configure Global Security_For _Markup Formatter_, select _Raw HTML_Click _Save_Go to _New Item_Item name: SomeProjectSelect _Inheritance Project_Click _OK_On the Configuration screen, under _Build Environment_ section, check _Mask passwords_Add name/password pair: - Name: SOME_PWD2 - Password: IShouldAlsoBeMaskedClick _Save_Add a short description in the text field of the dialog, then click _OK_Click _Build Now_Select the specific build under the _Build History_ sectionClick _View/Download full build flow_Under the _All build parameters_ section, the password values are shown.Also with the Download option the password values are exposed in the shell script export. 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] [mask-passwords-plugin] (JENKINS-33500) Masked passwords are shown for inheritance project
Title: Message Title Mark M created an issue Jenkins / JENKINS-33500 Masked passwords are shown for inheritance project Issue Type: Bug Assignee: Oleg Nenashev Attachments: build.sh, screen.png Components: mask-passwords-plugin, project-inheritance-plugin Created: 12/Mar/16 3:40 PM Environment: Jenkins v1.652 Mask Passwords Plugin v2.8 inheritance-plugin v1.5.3 Priority: Major Reporter: Mark M Masked Passwords are exposed from the View/Download full build flow page. Steps to reproduce: Go to Manage Jenkins --> Configure System Under Mask Passwords - Global name/password pairs section: Add name/password pair: Name: SOME_PWD Password: IShouldBeMasked Click Save
[JIRA] [workflow-plugin] (JENKINS-33499) Workflow EC2 Integration - build node not provisioned
Title: Message Title John Ament created an issue Jenkins / JENKINS-33499 Workflow EC2 Integration - build node not provisioned Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 12/Mar/16 2:59 PM Priority: Minor Reporter: John Ament When using the workflow plugin, EC2 nodes are not provisioned in parallel. Say that I have two parallel steps that both use a dynamically provisioned EC2 node. These two parallel steps request nodes in a serial fashion. When using the old pipeline plugin, the build jobs would each request a node and two nodes would get provisioned. When using the new workflow/pipeline plugin only a single node is provisioned when entering this step. The first step takes the node, and then a second node is requested against EC2. It would be ideal if the workflow plugin could request 2 nodes to be provisioned in parallel. Add Comment
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33498) Improve full screen view of pipeline stage view
Title: Message Title John Ament created an issue Jenkins / JENKINS-33498 Improve full screen view of pipeline stage view Issue Type: Improvement Assignee: Antonio Muñiz Components: pipeline-stage-view-plugin Created: 12/Mar/16 2:55 PM Priority: Minor Reporter: John Ament Even in full screen mode, the pipeline stage view is pretty small. It takes about 40% of the screen. Can you make it take up more screen real estate, maybe based on the number of stages in the pipeline? Add Comment
[JIRA] [checkstyle-plugin] (JENKINS-33472) Checkstyle Trend does not show up for Workflow scripts (Pipeline plugin)
Title: Message Title Ulli Hafner resolved as Duplicate Jenkins / JENKINS-33472 Checkstyle Trend does not show up for Workflow scripts (Pipeline plugin) Change By: Ulli Hafner Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Ludovic Fernandez commented on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax fix : https://github.com/jenkinsci/job-dsl-plugin/pull/783 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] [cucumber-testresult-plugin] (JENKINS-25728) "latest test results" not shown in project when last build failed
Title: Message Title Kanstantsin Shautsou commented on JENKINS-25728 Re: "latest test results" not shown in project when last build failed Kanstantsin Shautsou the issue you are describing is covered by JENKINS-31027. This issue was created in 2014 and JENKINS-31027 really later. 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] [cucumber-testresult-plugin] (JENKINS-25728) "latest test results" not shown in project when last build failed
Title: Message Title Kanstantsin Shautsou resolved as Postponed Hi, i'm not using anymore it and don't remember details. So closing issue. PS AFAIR it has no any configurations in comparison to other publishers. Jenkins / JENKINS-25728 "latest test results" not shown in project when last build failed Change By: Kanstantsin Shautsou Status: Open Resolved Resolution: Postponed 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-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Geoffroy Jabouley commented on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax I can manage the PR on monday, if you're ok with the fix: remove L183 to L185 of ScmContext.groovy What about extending a little bit the checks on test case "call git scm methods" to ensure defaults values for all fields? 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] [cucumber-testresult-plugin] (JENKINS-25728) "latest test results" not shown in project when last build failed
Title: Message Title James Nord commented on JENKINS-25728 Re: "latest test results" not shown in project when last build failed Kanstantsin Shautsou the issue you are describing is covered by JENKINS-31027. I'm still unsure what we can link to in "latestReport" if there is no report. Users will assume that the latest report will be for the report of the lastRun - but if I just link to the last run that generated a report then this will end up confusing the majority of users (its also not how other reporters work). Perhaps I should rename the latestReport to "report from latest build" and then that should make everything clearer? but now I am wondering what I am currently doing if a build is in flight 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-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Ludovic Fernandez edited a comment on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax With 0.43 & 0.44:- reproduce with Jenkins Job DSL Playground (http://job-dsl.herokuapp.com/)- reproduce with Jenkins ver. 1.642.1- not reproduce `./gradlew run -Pargs=job.dsl` 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-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Ludovic Fernandez edited a comment on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax I'm trying with 0.44:- not reproduce with tests or `./gradlew run -Pargs=job.dsl` With 0.43 & 0.44 :- reproduce with Jenkins Job DSL Playground (http://job-dsl.herokuapp.com/)- reproduce with Jenkins ver. 1.642.1- but not reproduce with tests or `./gradlew run -Pargs=job.dsl` 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-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Ludovic Fernandez commented on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax ScmContext.groovy#L184 it's the problem, you're right 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-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Ludovic Fernandez edited a comment on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax GitContext.groovy#L118 : it's the default value if the method is call but it's not call.ScmContext.groovy#L184 : It think not call in the test, it's the problem strange 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-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Geoffroy Jabouley commented on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax Thanks for your answers the test case "call git scm methods" does not seem to check anything but the remote and branch fields. https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/ScmContextSpec.groovy#L1173 But i'm not familiar with groovy testing. 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-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Ludovic Fernandez edited a comment on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax GitContext.groovy#L118 : it's the default value if the method is call but it's not call.ScmContext.groovy#L184 : like I say tests work properly, code is correct It think it's 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] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains whitespace
Title: Message Title Edgar Madrigal commented on JENKINS-24686 Re: scm-sync-configuration fails if job name contains whitespace I forgot to mention that there's some weird behaviour. If I do a change once I push and restart. Sometimes it doesn't register the change. I had to do a couple of changes and then it loads. Nuking the plug in completely also is a work around for me 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] [cucumber-testresult-plugin] (JENKINS-26340) Implement SimpleBuildStep for Pipeline Compatibility
Title: Message Title James Nord updated an issue Jenkins / JENKINS-26340 Implement SimpleBuildStep for Pipeline Compatibility Change By: James Nord Summary: Implement SimpleBuildStep for Workflow Pipeline Compatibility 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-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Ludovic Fernandez commented on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax GitContext.groovy#L118 : it's the default value if the method is call but it's not call. ScmContext.groovy#L184 : like I say tests work properly, code is correct 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] [violations-plugin] (JENKINS-33028) Violations report does not show per-file report
Title: Message Title Tim Ellerton commented on JENKINS-33028 Re: Violations report does not show per-file report Experience the same issue with pylint. 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-33497) SCM check via subversion continues triggering new builds - even with no changes
Title: Message Title Lars Engelhard created an issue Jenkins / JENKINS-33497 SCM check via subversion continues triggering new builds - even with no changes Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 12/Mar/16 9:43 AM Environment: Debian 8.3.0 on AMD 64Bit Intel DN2800MT2 hardware, headless server, dedicated to Jenkins. SVN hosted on different dedicated hardware. No virtualization. Priority: Major Reporter: Lars Engelhard Running latest version of Jenkins (1.652) and SVN Plugin (2.5.7). I configured five Matrix projects with dimension OS = linux windows and BIT = 32 64 I noticed that my machine got building 24/7 not able to clear the stack once I updated to the latest versions indicated in Jenkins configuration. All worked fine and well in the previous version. I checked the reason and figured out that Jenkins checked the SCM using SVN Plugin once per hour (as I configured), but claimed an SVN change each time (in the log) triggering the build. However, the revision number stayed the same! here is what the config tells me about the trigger (locales in german, you get the idea from the english part I am sure): Started on 12.03.2016 09:29:00 Arbeitsbereich enthält https://.org:443/repos//trunk nicht. Neuer Build
[JIRA] [core] (JENKINS-33495) Separate scrollspy widget code out from tab widget code
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-33495 Separate scrollspy widget code out from tab widget code Change By: Tom FENNELLY The new scrollspy widget code was pasted in on top of the tab widget code. It should be separated out into a dedicated widget, leaving the tab widget as a a tab widget. 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-33495) Separate scrollspy widget code out from tab widget code
Title: Message Title Tom FENNELLY started work on JENKINS-33495 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33496) Add tests for scrollspy widget
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-33496 Add tests for scrollspy widget Issue Type: Story Assignee: Tom FENNELLY Components: core Created: 12/Mar/16 9:27 AM Labels: 2.0 Priority: Major Reporter: Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-33495) Separate scrollspy widget code out from tab widget code
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-33495 Separate scrollspy widget code out from tab widget code Issue Type: Story Assignee: Tom FENNELLY Components: core Created: 12/Mar/16 9:25 AM Labels: 2.0 Priority: Major Reporter: Tom FENNELLY The new scrollspy widget code was pasted in on top of the tab widget code. It should be separated out into a dedicated widget, leaving the tab widget as a a tab widget. Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Geoffroy Jabouley edited a comment on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax Maybe the default value shall be set to false here:https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/scm/GitContext.groovy#L118 Or this line is wrong:https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/ScmContext.groovy#L184 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-33482) Git scm option "Create tag for each build" is activated by default for oneliner syntax
Title: Message Title Geoffroy Jabouley commented on JENKINS-33482 Re: Git scm option "Create tag for each build" is activated by default for oneliner syntax Maybe the default value shall be set to false here: https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/scm/GitContext.groovy#L118 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.
