[JIRA] [git-client-plugin] (JENKINS-25999) Unable to clone GitLab repository after updated to plugin version 1.12.0
Sergii Kozak closed JENKINS-25999 as Cannot Reproduce Unable to clone GitLab repository after updated to plugin version 1.12.0 Hi again, after I registered this issue I was still doubting that everything I have done before was completely correct. Then I decided to perform couple of "retries", and after third attempt to make the configuration of Jenkins build job from scratch I've figured out the mistake was present with regard to SSH private keys, used to authenticate against GitLab. After I corrected that used SSH key in Jenkins, it (repository clone) started working OK. So no issues at the end, and I apologize for the disturbing for (basically) no reason. Change By: Sergii Kozak (12/Dec/14 8:12 AM) Status: InProgress Closed Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-17457) get a non-existing directory problem when making an IPA after building a workspace.
lacostej updated JENKINS-17457 get a non-existing directory problem when making an IPA after building a workspace. A project exhibiting the issue Change By: lacostej (12/Dec/14 8:54 AM) Attachment: JENKINS-17457.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26020) Will not start builds even though there are available slots on executor
Christian Bremer commented on JENKINS-26020 Will not start builds even though there are available slots on executor 200$ is up for grabs for this issue at: https://freedomsponsors.org/issue/598/will-not-start-builds-even-though-there-are-available-slots-on-executor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xfpanel-plugin] (JENKINS-26006) Can't change background color
Alexander Wenzel commented on JENKINS-26006 Cant change background color I can confirm that changing build colours has no effect since the last plugin update (1.2.3). Note: After reverting to 1.2.2 it works again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-26040) Differentiate iterations of a scenario outline in the results
Dominic Bishop created JENKINS-26040 Differentiate iterations of a scenario outline in the results Issue Type: New Feature Assignee: James Nord Attachments: AccountNumberValidation.feature, report.json Components: cucumber-testresult-plugin Created: 12/Dec/14 9:46 AM Description: If a feature contains a "Scenario Outline" then the results of this are displayed as a list of scenarios all with the same name. It would be nice if these were uniquely identified in the results displayed, possibly by appending an iteration number to the name, e.g. #1, #2 etc to represent which iteration of the outline the scenario is for. Looking at the JSON generated the iteration number is contained as part of the id value against the scenario result. I have attached a simple feature file and the corresponding JSON results file that demonstrates how a scenario outline is displayed. Environment: Jenkins 1.580.1 Project: Jenkins Priority: Minor Reporter: Dominic Bishop This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-26040) Differentiate iterations of a scenario outline in the results
Dominic Bishop updated JENKINS-26040 Differentiate iterations of a scenario outline in the results Change By: Dominic Bishop (12/Dec/14 9:46 AM) Issue Type: NewFeature Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-23902) Matrix parent takes executor slot and blocks children
James Howe closed JENKINS-23902 as Fixed Matrix parent takes executor slot and blocks children Change By: James Howe (12/Dec/14 9:57 AM) Status: Reopened Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-20925) No trigger for Unstable - Failure
James Howe closed JENKINS-20925 as Fixed No trigger for Unstable - Failure Change By: James Howe (12/Dec/14 9:58 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-21569) Expose current input line in groovy script
James Howe closed JENKINS-21569 as Fixed Expose current input line in groovy script Change By: James Howe (12/Dec/14 9:58 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-17565) Support job display names in bot commands
James Howe closed JENKINS-17565 as Fixed Support job display names in bot commands Change By: James Howe (12/Dec/14 9:59 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-20658) All builds that were using GNU Make + GCC now fail
James Howe closed JENKINS-20658 as Fixed All builds that were using GNU Make + GCC now fail Change By: James Howe (12/Dec/14 9:59 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-perf-plugin] (JENKINS-26041) No data exists after successful run
Dominic Bishop created JENKINS-26041 No data exists after successful run Issue Type: Bug Assignee: Unassigned Attachments: AccountNumberValidation.feature, report.json Components: cucumber-perf-plugin Created: 12/Dec/14 10:01 AM Description: I have a problem where selecting the Performance Report link shows a message of "No data exists for Cucumber test runs, or the job is currently building. You may need to perform a build of your Cucumber testing project." despite the build completing successfully. To reproduce this I created a simple job which has a cucumber JSON report file in the root of the workspace named report.json and added a post build action to generate the performance report. The JSON file and the feature file that originally created it are attached. The console log for the build appears to show everything as successful: Started by user anonymous Building in workspace /opt/jenkins/data/jobs/Cucumber_Performance_Test/workspace workspace $ /bin/sh -xe /tmp/hudson4566208210991663498.sh + touch report.json CucumberPerfRecorder Starting Cucumber Performance Report generation... CucumberPerfRecorder Reporting on performance for Cucumber_Performance_Test #1 CucumberPerfRecorder detected master build looking in /opt/jenkins/data/jobs/Cucumber_Performance_Test/workspace found files CucumberPerfRecorder running project reports on 1 builds CucumberPerfRecorder project report generation complete Finished: SUCCESS There are no errors logged in the Jenkins log during the build or when accessing the reports link. I have tried a couple of additional runs of the job in case more than one run was needed to produce reports but it still shows the same error. Environment: Jenkins 1.580.1 Cucumber Performance Plugin 2.0.6 Project: Jenkins Priority: Major Reporter: Dominic Bishop This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-23152) builds getting lost due to GerritTrigger
rsandell commented on JENKINS-23152 builds getting lost due to GerritTrigger I am working on a fix on this branch https://github.com/jenkinsci/gerrit-trigger-plugin/tree/JENKINS-23152 and am close to done. It should be ready enough for beta testing if you can build it yourself. Still have a bunch of findbugs issues to fix and get feedback from the other maintainers since this fix does fundamental changes in the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event
rsandell commented on JENKINS-26010 Workflow plugin not working with with Gerrit event The Gerrit Trigger code is littered with assumptions about AbstractProject to reliably "just change the type" without doing an aggressive search replace and fix issues as they arise. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-17457) get a non-existing directory problem when making an IPA after building a workspace.
lacostej commented on JENKINS-17457 get a non-existing directory problem when making an IPA after building a workspace. Here are my findings so far: 1- if we don't specify the -configuration argument, as the plugin doesn't try to infer xcodebuild defaults configuration for the command line, the plugin creates an invalid buildDirectory 2- we could try to extract this information from the project/workspace, but I haven't managed to get xcodebuild to behave as it says it should when building a project without specifying the configuration (I mailed the xcode-users list about it for clarification, the conversation will appear on http://lists.apple.com/archives/xcode-users/2014/Dec/index.html) 3- if you don't specify the BUILD_CONFIGURATION_DIR, xcode will build under some temporary directory that isn't under jenkins workspace (DerivedData etc). So even if jenkins created (mkdir) the missing default directory given "default configuration (infered) + buildPlatform" it isn't searching for the build apps under the right directory ListFilePath apps = buildDirectory.list(new AppFileFilter()); 4- the ipa directory will be under the build configuration dir I have to think about it more, but I think the simplest is to force the user to specify the BUILD_CONFIGURATION_DIR when selecting the generate IPA option or provide a good default. I am not sure why the other case (let xcode use his own DerivedData dirs) would be useful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-17457) get a non-existing directory problem when making an IPA after building a workspace.
lacostej edited a comment on JENKINS-17457 get a non-existing directory problem when making an IPA after building a workspace. Here are my findings so far: if we don't specify the -configuration argument, as the plugin doesn't try to infer xcodebuild defaults configuration for the command line, the plugin creates an invalid buildDirectory we could try to extract this information from the project/workspace, but I haven't managed to get xcodebuild to behave as it says it should when building a project without specifying the configuration (I mailed the xcode-users list about it for clarification, the conversation will appear on http://lists.apple.com/archives/xcode-users/2014/Dec/index.html) if you don't specify the BUILD_CONFIGURATION_DIR, xcode will build under some temporary directory that isn't under jenkins workspace (DerivedData etc). So even if jenkins created (mkdir) the missing default directory given "default configuration (infered) + buildPlatform" it isn't searching for the build apps under the right directory ListFilePath apps = buildDirectory.list(new AppFileFilter()); the ipa directory will be under the build configuration dir I have to think about it more, but I think the simplest is to force the user to specify the BUILD_CONFIGURATION_DIR when selecting the generate IPA option or provide a good default. I am not sure why the other case (let xcode use his own DerivedData dirs) would be useful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Alan Birtles
commented on JENKINS-21640
scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0
I've found a temporary workaround by running the following script as a daily job:
cp ${JENKINS_HOME}/*.xml ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/
rsync -avm --include='config.xml' -f 'hide,! */' ${JENKINS_HOME}/jobs/ ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/
svn add --force ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/
if svn status ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/ | grep '^[AMCDG]' ; then
svn ci ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/ -m ""
else
echo "No changes found"
fi
It's not quite as good as the scm sync but it does the job
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26042) Highlight most recent build in Dashboard
Alexandru Gheorghe created JENKINS-26042 Highlight most recent build in Dashboard Issue Type: Improvement Assignee: Unassigned Components: core Created: 12/Dec/14 10:26 AM Description: In All view inside the main dashboard page, after a recent (scheduled or not) build has been completed, it can be highlighted to reflect the result. For example, I've 10 builds, only 1 runs as a cron based job, after it has build, can be highlighted with either blue background, red or yellow. Let the highlight last only for 30 minutes or 1 hour to avoid having all the builds highlighted so readability is maintained after a while. The highlight reflects last build (most recent) status (red, blue, yellow). Environment: Jenkins ver. 1.593; OpenJDK Project: Jenkins Priority: Minor Reporter: Alexandru Gheorghe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26042) Highlight most recent build in Dashboard
Alexandru Gheorghe
updated JENKINS-26042
Highlight most recent build in Dashboard
Change By:
Alexandru Gheorghe
(12/Dec/14 10:27 AM)
Description:
h3.Summary
In{{All}}viewinsidethemaindashboardpage,afterarecent(scheduledornot)buildhasbeencompleted,itcanbehighlightedtoreflecttheresult.
h3.Scenario
Forexample,Ive10builds,only1runsasacronbasedjob,afterithas
build
built
,canbehighlightedwitheitherbluebackground,redoryellow.Letthehighlightlastonlyfor30minutesor1hourtoavoidhavingallthebuildshighlightedsoreadabilityismaintainedafterawhile.Thehighlightreflectslastbuild(mostrecent)status(red,blue,yellow).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-pullrequest-builder-plugin] (JENKINS-26043) Have jenkins approve the pull request on successful build
Anton Lundin
created JENKINS-26043
Have jenkins approve the pull request on successful build
Issue Type:
Bug
Assignee:
Unassigned
Components:
bitbucket-pullrequest-builder-plugin
Created:
12/Dec/14 10:55 AM
Description:
It would be awesome if there were a option to have jenkins to "approve" the pull request if it the build succeeds.
With approval i don't mean "merge" the pull request, just sett the approval flag.
This is done by a POST to https://api.bitbucket.org/2.0/repositories/{owner}/{repo_slug}/pullrequests/{id}/approve
Project:
Jenkins
Priority:
Minor
Reporter:
Anton Lundin
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [description-setter-plugin] (JENKINS-25928) Version number plugin corrupts build history output
Dirk Heinrichs commented on JENKINS-25928 Version number plugin corrupts build history output Seems to be a duplicate of JENKINS-24589 which has been fixed in 1.593. However, build history is still not showing correctly, since all HTML tags in the build description seem to be ignored now. For example, we put links to test results into the build description, so that users can get to them directly from the build history. Now, we'd need to first go to the builds status page first, which displays the build description correctly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [description-setter-plugin] (JENKINS-25928) Version number plugin corrupts build history output
Dirk Heinrichs updated JENKINS-25928 Version number plugin corrupts build history output Change By: Dirk Heinrichs (12/Dec/14 11:30 AM) Component/s: description-setter-plugin Component/s: versionnumber-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20998) Add Timestamp to Workspace View
Bruno P. Kinoshita commented on JENKINS-20998 Add Timestamp to Workspace View A patch has been submitted to the dev-list 1, but the developer has no JIRA or GitHub account. Just in case someone here is willing to test the patch, provide some feedback and submit a PR. Cheers, Bruno. 1 https://groups.google.com/forum/#!topic/jenkinsci-dev/cr_ZpR2EMlw This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot-plugin] (JENKINS-9880) fixing of plot group, 'spaces', bug and addition of 'specify color' feature.
Arpit Nagar commented on JENKINS-9880 fixing of plot group, spaces, bug and addition of specify color feature. Is someone looking into it ?? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xfpanel-plugin] (JENKINS-26006) Can't change background color
Bruno Teixeira commented on JENKINS-26006 Cant change background color Yes, after reverting i'm able to configure the plugin again, thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing-plugin] (JENKINS-19651) Config Slicing Gradle version per project yields stack trace output
Torsten Krah edited a comment on JENKINS-19651 Config Slicing Gradle version per project yields stack trace output Hi, got this with current Jenkins 1.593 and Gradle Plugin 1.24 and Slicing Plugin 1.40. javax.servlet.ServletException: java.lang.NoSuchMethodError: hudson.plugins.gradle.Gradle.init(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Z)V at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) 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:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85) 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 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at
[JIRA] [configurationslicing-plugin] (JENKINS-19651) Config Slicing Gradle version per project yields stack trace output
Torsten Krah reopened JENKINS-19651 Config Slicing Gradle version per project yields stack trace output Hi, got this with current Jenkins 1.593 and Gradle Plugin 1.24 and Slicing Plugin 1.40. javax.servlet.ServletException: java.lang.NoSuchMethodError: hudson.plugins.gradle.Gradle.init(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Z)V at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) 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:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85) 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 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at
[JIRA] [configurationslicing-plugin] (JENKINS-26044) Ant version per project fails to change via Configuration Slicing (AntSlicer)
Torsten Krah created JENKINS-26044 Ant version per project fails to change via Configuration Slicing (AntSlicer) Issue Type: Bug Assignee: mdonohue Components: configurationslicing-plugin Created: 12/Dec/14 2:23 PM Description: Installed the configuration slicing plugin and tried to change my "Ant version per Project". I've putting some project from "Default" to "Ant 1.9.4" and "Saving" the page - but after looking back at the configuration nothing have changed. In contrast i've tried it with "JDK per project" - that worked - but not for Ant. There is no error message on the page, neither in the logs when trying to change the Ant configuration. Environment: Jenkins 1.593, Slicing-Plugin 1.40 Project: Jenkins Labels: plugins slicing ant Priority: Major Reporter: Torsten Krah This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer-plugin] (JENKINS-26045) Connecting to Remote WAS 7 Network Deployment errors
Sean Moriarty created JENKINS-26045 Connecting to Remote WAS 7 Network Deployment errors Issue Type: Bug Assignee: Unassigned Components: websphere-deployer-plugin Created: 12/Dec/14 2:43 PM Description: Any help would be greatly appreciated. I am getting the following error where I can't connect to the remote port on SOAP port 8879. This appears to be certificate issues. I created extracted the certificates for 9043 and 8879. I used I have many combinations of creating a separate jssecerts, Batch file E:\AppDevelopment\jdk\IBM\jdk60\bin\java.exe InstallCert server:9043 pause E:\AppDevelopment\jdk\IBM\jdk60\bin\java.exe InstallCert server:8879 pause echo LIST Trust store certs to get the alias names call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -list -storepass WebAS -v -keystore "E:\AppDevelopment\Process\WAS_Deploy\dia-dev1\DummyClientTrustFile.jks" DummyClientTrustFilecertList.txt echo list of alias: "thawte personal freemail ca" "new websphere dummy client" "new websphere dummy server" "default_signer" "thawte personal basic ca" "rsa secure server certification authority" "thawte premium server ca" echo "verisign class 1 public primary certification authority" "thawte server ca" pause echo EXPORT CERTS call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -export -storepass WebAS -alias "thawte personal freemail ca" -keystore E:\AppDevelopment\Process\WAS_Deploy\dia-dev1\DummyClientTrustFile.jks -file thawtepersonalfreemailca.crt call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -export -storepass WebAS -alias "new websphere dummy client" -keystore E:\AppDevelopment\Process\WAS_Deploy\dia-dev1\DummyClientTrustFile.jks -file newwebspheredummyclient.crt call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -export -storepass WebAS -alias "new websphere dummy server" -keystore E:\AppDevelopment\Process\WAS_Deploy\dia-dev1\DummyClientTrustFile.jks -file newwebspheredummyserver.crt call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -export -storepass WebAS -alias "default_signer" -keystore E:\AppDevelopment\Process\WAS_Deploy\dia-dev1\DummyClientTrustFile.jks -file default_signer.crt call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -export -storepass WebAS -alias "thawte personal basic ca" -keystore E:\AppDevelopment\Process\WAS_Deploy\dia-dev1\DummyClientTrustFile.jks -file thawtepersonalbasicca.crt call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -export -storepass WebAS -alias "rsa secure server certification authority" -keystore E:\AppDevelopment\Process\WAS_Deploy\dia-dev1\DummyClientTrustFile.jks -file rsasecureservercertificationauthority.crt call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -export -storepass WebAS -alias "thawte premium server ca" -keystore E:\AppDevelopment\Process\WAS_Deploy\dia-dev1\DummyClientTrustFile.jks -file thawtepremiumserverca.crt call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -export -storepass WebAS -alias "verisign class 1 public primary certification authority" -keystore E:\AppDevelopment\Process\WAS_Deploy\dia-dev1\DummyClientTrustFile.jks -file verisignclass1publicprimarycertificationauthority.crt call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -export -storepass WebAS -alias "thawte server ca" -keystore E:\AppDevelopment\Process\WAS_Deploy\dia-dev1\DummyClientTrustFile.jks -file thawteserverca.crt echo IMPORT CERTS call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -import -storepass changeit -trustcacerts -alias "thawte personal freemail ca" -file E:\AppDevelopment\Process\WAS_Deploy\thawtepersonalfreemailca.crt -keystore E:\AppDevelopment\Process\WAS_Deploy\cacerts call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -import -storepass changeit -trustcacerts -alias "new websphere dummy client" -file E:\AppDevelopment\Process\WAS_Deploy\newwebspheredummyclient.crt -keystore E:\AppDevelopment\Process\WAS_Deploy\cacerts call "E:\Program Files (x86)\Jenkins\jre\bin\keytool" -import -storepass changeit -trustcacerts -alias "new websphere dummy server" -file E:\AppDevelopment\Process\WAS_Deploy\newwebspheredummyserver.crt -keystore
[JIRA] [http_request] (JENKINS-21994) Add HTTP header
Jeff G commented on JENKINS-21994 Add HTTP header I was surprised to see that assigning headers to the request was not already a built in feature to this plugin. This will prevent me from being able to use this plugin. I have not found any other plugins which could run as a build step using headers so I will have to resort to bash with wget. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [http_request] (JENKINS-26046) Wiki 'open issues' link brings to component 'http_request-plugin' instead of 'http_request'
Daniel Beck resolved JENKINS-26046 as Not A Defect Wiki open issues link brings to component http_request-plugin instead of http_request Not a defect in the plugin. (File wiki issues in the INFRA project.) And since I'll rename that component soon (planned for weeks but didn't have the time) anyway, there's no need to act on this, so I'm resolving rather than moving to INFRA Change By: Daniel Beck (12/Dec/14 3:49 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26015) Layout broken since 1.593
Daniel Beck updated JENKINS-26015 Layout broken since 1.593 To clarify, "logged" is short for "logged in"? And it only happens in Chrome 39? Are you using the Simple Theme plugin and have some custom CSS applied? Change By: Daniel Beck (12/Dec/14 3:52 PM) Labels: 1.593chromecssfirefoxiejellyjenkinslayout user-experience This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-26012) Multuple Parameters links
Daniel Beck updated JENKINS-26012 Multuple Parameters links Change By: Daniel Beck (12/Dec/14 3:53 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-23152) builds getting lost due to GerritTrigger
Jesse Glick commented on JENKINS-23152 builds getting lost due to GerritTrigger It is a good idea to create a PR from the branch—makes it easier for people to comment on individual diff lines. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26039) Workflow support for post build plugin (like violation, irc, ext. mail)
Jesse Glick resolved JENKINS-26039 as Not A Defect Workflow support for post build plugin (like violation, irc, ext. mail) The step metastep is used for this, but the plugin with the post-build step needs to be updated to implement SimpleBuildStep, which has only been done in a few cases so far. (Or it can implement a Workflow step directly, when that is more appropriate.) Best to file a separate issue in each plugin for which you need Workflow integration (just add the workflow label for tracking). Change By: Jesse Glick (12/Dec/14 4:02 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26033) Document and test return value for parallel
Jesse Glick
updated JENKINS-26033
Document and test return value for parallel
I am tempted to say that the return value should just be null (unused). If you actually need to track the result of various branches, it is clearer to do so directly. For example:
def x, y
parallel one: {x = 1}, two: {y = 2}
echo "x+y = ${x+y}"
This also makes it obvious how to track exceptions in branches:
def result
parallel main: {
try {
node {sh 'false'}
result = 'success'
} catch (x) {
result = "error: ${x}"
}
}
echo result
Change By:
Jesse Glick
(12/Dec/14 4:13 PM)
Assignee:
JesseGlick
KohsukeKawaguchi
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26034) Add support for sibling-cancel in parallel().
Jesse Glick updated JENKINS-26034 Add support for sibling-cancel in parallel(). It sounds like parallel returns a map from job-label to job-status. Currently to branch return value (not a status per se), but see my comment in JENKINS-26033. the job-status would be "failed" for the job that failed, and "cancelled" for the sibling jobs that were cancelled. There is only one “job”, the workflow as a whole, a build of which is marked as a failure if any of the parallel branches fail—unless you have a try/catch block outside parallel which does something else. Change By: Jesse Glick (12/Dec/14 4:19 PM) Assignee: JesseGlick KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-26047) Add parameter to parameterized trigger parameters to allow selection of configured remote hosts
Craig Phillips created JENKINS-26047 Add parameter to parameterized trigger parameters to allow selection of configured remote hosts Issue Type: New Feature Assignee: Maurice W. Components: parameterized-remote-trigger-plugin Created: 12/Dec/14 4:19 PM Description: When you select the build parameters in the project configuration page, you get things like String, Boolean, Node, Label, etc. It would be useful to have an option for selecting one of the configured remote trigger hosts, so we don't have to duplicate references to these. For example, if you wanted to reference the remote machine from a script, you might want the remote trigger host to be stored in an environment variable: REMOTE_TRIGGER_HOST="http://some-jenkins-server:8080/" The only way to do this, is to duplicate the server name and define it as a String parameter. Project: Jenkins Priority: Minor Reporter: Craig Phillips This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
Jesse Glick resolved JENKINS-22641 as Fixed Jenkins no longer kills running processes after job fails Don Bogardus then your issue is probably a distinct bug with a similar symptom but potentially distinct preconditions and root cause. Better to file it as a new ticket, with any steps to reproduce you can muster, and mark it as “blocking” this one. Change By: Jesse Glick (12/Dec/14 4:21 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-26032) Prefer BuildStepMonitor.NONE
Jesse Glick updated JENKINS-26032 Prefer BuildStepMonitor.NONE Change By: Jesse Glick (12/Dec/14 4:23 PM) Summary: Prefer BuildStepMonitor. BUILDmakesconcurrentbuildswait,couldbechangedtoBuildStepMonitor. NONE ? Labels: concurrent-build Assignee: JesseGlick ManuelCarrasco Component/s: performance-plugin Component/s: email-ext-plugin URL: https://github.com/jenkinsci/email-ext-plugin/pull/79 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Don Bogardus created JENKINS-26048 Jenkins no longer cleaning up child processes when build stopped - as of 1.587 Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Dec/14 5:01 PM Description: Similar to bug 22641, Jenkins no longer cleaning up surefire executions when a job is stopped. To reproduce : Start any job with a surefire execution, once the tests start running, stop the job through the jenkins interface. The surefire process continues to run. Just like bug 22641, this behavior started in 1.553, was resolved in 1.565.2, then started again in 1.587. Rating this as critical because processes build up eventually causing issues with running out of memory or hitting the nproc limit. Environment: CentOS 6, JRE 7 or 8 Project: Jenkins Priority: Critical Reporter: Don Bogardus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26033) Document and test return value for parallel
Craig Silverstein commented on JENKINS-26033 Document and test return value for parallel This makes sense to me. (I wonder how this design decision would affect JENKINS-26034, but I'll put my comments about that there.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Don Bogardus updated JENKINS-26048 Jenkins no longer cleaning up child processes when build stopped - as of 1.587 Change By: Don Bogardus (12/Dec/14 5:47 PM) Description: Similartobug22641,Jenkinsnolongercleaningup surefireexecutions childprocesses whenajobisstopped.Toreproduce:Startanyjobwithasurefireexecution,oncethetestsstartrunning,stopthejobthroughthejenkinsinterface.Thesurefireprocesscontinuestorun.Justlikebug22641,thisbehaviorstartedin1.553,wasresolvedin1.565.2,thenstartedagainin1.587.Ratingthisascriticalbecauseprocessesbuildupeventuallycausingissueswithrunningoutofmemoryorhittingthenproclimit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25934) Add ability to set a comment with any installed plugin or lock a plugin
Daniel Beck
commented on JENKINS-25934
Add ability to set a comment with any installed plugin or lock a plugin
Appears to be a use case with very limited appeal to most users. ("Skip this version" may be better anyway.) May be possible to add in a plugin, once plugin manager columns are made extensible, which they are not at the moment.
Possible workarounds:
If you know how, create a build identical to your version of mercurial plugin but give it a special version number as indicator that it's super special and should not be replaced without thinking.
Simple Theme plugin may allow you to add that bit of CSS/JS
If you have Jenkins Enterprise, check out Update Center Plugin to run your own UC with only approved updates provided
Filter the JSON received from updates.jenkins-ci.org to exclude mercurial in some way, e.g. through a proxy, or by running a Groovy script in Jenkins that discards the mercurial update info from memory.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26034) Add support for sibling-cancel in parallel().
Craig Silverstein
commented on JENKINS-26034
Add support for sibling-cancel in parallel().
Sorry, I knew I'd get the terminology wrong!
It sounds from JENKINS-26033 that you're leaning towards not having a (meaningful) return value from 'branch'. So if I want to record the fact a particular branch failed, I'd have to swallow the exception and rethrow (to cause the sibling-cancel) at least, I assume the rethrow would cause the sibling-cancel.
Just thinking out loud about the following use-case: I want to run two tasks in parallel. If either one fails, I want to cancel the other, and then continue executing my job. How would I do that in a world where 'cancel_siblings' was an option to 'parallel'. I guess it would be something like this:
def one_failed, two_failed;
try {
parallel one: {
try {
...
} catch (x) {
_one_failed_ = true
// Need to rethrow to cause parallel to cancel job two
rethrow // I assume this is a thing?
}
}, two: {
try {
...
} catch (x) {
two_failed = true
rethrow
}
}
} catch (x) {
}
... continue on, looking at one_failed and two_failed if needed ...
It's a little messy but I believe it works. I doubt this is a super-common case, so as long as it's possible I think this design works for our needs, at least.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [extensible-choice-parameter-plugin] (JENKINS-26049) Input widget for Groovy script needs to be textarea first time showing uploaded job.
Mark Chance created JENKINS-26049 Input widget for Groovy script needs to be textarea first time showing uploaded job. Issue Type: Bug Assignee: Unassigned Attachments: config.xml Components: extensible-choice-parameter-plugin Created: 12/Dec/14 6:18 PM Description: I am creating a job via the API which has configured this plugin and the System Groovy Choice Parameter. The groovy script is part of the job configuration XML, however it gets "corrupted" upon upload. I believe the problem is that the default input widget is a input type='text' control which strips out the \n characters. After I use the GUI to change it to a text area, it stays that way. I don't know how it knows or how it make it a textarea the first time through. Project: Jenkins Priority: Major Reporter: Mark Chance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extensible-choice-parameter-plugin] (JENKINS-26049) Input widget for Groovy script needs to be textarea first time showing uploaded job.
Mark Chance closed JENKINS-26049 as Not A Defect Input widget for Groovy script needs to be textarea first time showing uploaded job. I was stripping out the \n myself. Change By: Mark Chance (12/Dec/14 6:34 PM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25393) UI: Build History box looks bad with medium to long build labels
Ioannis Moutsatsos edited a comment on JENKINS-25393 UI: Build History box looks bad with medium to long build labels This look really nice in 1.593! Thank you for fixing this. Although it might have looked as I have been using descriptions for build names, this is is not the case. Our build names are indeed long since they have to reflect the workflow that a data set we are analyzing has gone through. I'm very pleased with you current implementation. I hope it gets rolled into an LTS release soon! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25393) UI: Build History box looks bad with medium to long build labels
Ioannis Moutsatsos commented on JENKINS-25393 UI: Build History box looks bad with medium to long build labels This look really nice! Thank you for fixing this. Although it might have looked as I have been using descriptions for build names, this is is not the case. Our build names are indeed long since they have to reflect the workflow that a data set we are analyzing has gone through. I'm very pleased with you current implementation. I hope it gets rolled into an LTS release soon! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [elasticbox-plugin] (JENKINS-25978) Workflow integration
Phong Le assigned JENKINS-25978 to Phong Le Workflow integration Change By: Phong Le (12/Dec/14 6:59 PM) Assignee: PhongLe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-26050) Workflow integration
Jesse Glick created JENKINS-26050 Workflow integration Issue Type: New Feature Assignee: huybrechts Components: parameterized-trigger-plugin Created: 12/Dec/14 7:05 PM Description: Currently hudson.plugins.parameterizedtrigger.BuildTriggerConfig and related classes is designed to assume that the downstream project is an AbstractProject, preventing it from triggering a WorkflowJob in schedule (see also perform, perform2, DescriptorImpl.doCheckProjects, etc.). This could probably be relaxed by just checking for a Job Queue.Task from which you can schedule a job with a little difficulty (check ParameterizedJob.getQuietPeriod and Job.isBuildable); or perhaps SCMTriggerItem whose scheduleBuild2 is more convenient. Should work smoothly for TriggerBuilder. For BuildTrigger, can work to the extent that canDeclare is made to be false, so that the triggering is done explicitly rather than via DependencyDeclarer (and thus the DependencyGraph, which at least for now is restricted to AbstractProject). Project: Jenkins Labels: workflow Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-24673) Build wrappers in Workflow plugin
Jesse Glick commented on JENKINS-24673 Build wrappers in Workflow plugin Build wrappers could perhaps be integrated by defining a SimpleBuildWrapper API (analogous to SimpleBuildStep and so taking Run and FilePath rather than AbstractBuild) where Environment is considered Serializable, and introducing a generic Step to run these. This could make it easier to use xvnc-plugin etc. The tool-env plugin does not need this, due to the standard tool step. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-binding-plugin] (JENKINS-26051) Workflow integration
Jesse Glick created JENKINS-26051 Workflow integration Issue Type: New Feature Assignee: Jesse Glick Components: credentials-binding-plugin Created: 12/Dec/14 7:12 PM Description: A replacement for SecretBuildWrapper that is a Step (with invokeBodyLater) rather than a BuildWrapper, probably returning the binding(s) in a map. Means some API changes to Binding. bind must take a FilePath workspace (and maybe Run run) rather than AbstractBuild build. And Environment must be declared Serializable, since unbind may be called in another session. Project: Jenkins Labels: workflow api Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Richard Pijnenburg commented on JENKINS-25944 Version 1.0.2 fails with stacktrace I've just installed it on one of our jenkins installations and works like a charm. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-binding-plugin] (JENKINS-26051) Workflow integration
Jesse Glick commented on JENKINS-26051 Workflow integration Not to be confused with credentials support in a Step or a compatible SCM or SimpleBuildStep implementation: this is about not just picking a credentialsId to pass on to another Step, but using the secrets held in the Credentials directly in some other way, such as in sh. Current workaround is to define a credentials parameter for the flow, giving it a default value. This means that Build Now is replaced with Build with Parameters, even though you do not need to actually do anything except confirm, which is unfortunate. (Scheduled builds should still run fine.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [elasticbox-plugin] (JENKINS-25978) Workflow integration
Jesse Glick commented on JENKINS-25978 Workflow integration Cf.: https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26034) Add support for sibling-cancel in parallel().
Jesse Glick
commented on JENKINS-26034
Add support for sibling-cancel in parallel().
if I want to record the fact a particular branch failed
You mean, beyond the build log and any flow graph visualizations that show this information, you want to base some decision for the remainder of the flow on which part failed, rather than having the whole build abort then and there. You could do something like
def oneErr, twoErr
try {
parallel one: {
try {
…
} catch (x) {
_oneErr_ = x
throw x // or anything for that matter
}
}, two: {
try {
…
} catch (x) {
twoErr = x
throw x
}
}
} catch (x) {
if (oneErr) {
…
} else if (twoErr) {
…
} else {
// something else went wrong, die
throw x
}
}
Perhaps not the most concise idiom, but the purpose is probably apparent to anyone reading it, and it is not hard to see how you could customize some aspects of the behavior.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26052) Fork without join
Jesse Glick
created JENKINS-26052
Fork without join
Issue Type:
New Feature
Assignee:
Kohsuke Kawaguchi
Components:
workflow-plugin
Created:
12/Dec/14 7:41 PM
Description:
Some flows have a need to start some long-running branches where we do not really care about waiting for termination. They might be running informational tests that would not fail the main job, or sending notifications, etc. Using parallel for these is awkward because you have to put the entire remainder of the flow in another branch, which does not nest nicely, etc.
Suggest an alternate fork {...} which runs some stuff in the background. Could return a Future-like object you could decide to wait on later if you wished. Possibly needed parameters:
A label, to be used as the thread name; perhaps optional, with some generated default.
A daemon flag. If off, there would be an implicit join at the end of the flow. If on, if the flow reaches the end and the thread is still running, it would be stop-ped (but we probably still need to wait for it to exit cleanly).
There should be a bounding box for the fork that runs inside so that the exit from the block is contingent on every fork inside to terminate.
Potentially this could allow parallel to be implemented as a library.
Project:
Jenkins
Labels:
parallel
Priority:
Major
Reporter:
Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-26054) FileMonitoringTask based on ProcStarter
Jesse Glick created JENKINS-26054 FileMonitoringTask based on ProcStarter Issue Type: New Feature Assignee: Jesse Glick Components: durable-task-plugin Created: 12/Dec/14 7:46 PM Description: Given a ProcStarter you should be able to get a FileMonitoringTask that runs that process in a platform-appropriate way. Project: Jenkins Labels: api Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-26053) Handle ConsoleAnnotator
Jesse Glick created JENKINS-26053 Handle ConsoleAnnotator Issue Type: New Feature Assignee: Jesse Glick Components: durable-task-plugin Created: 12/Dec/14 7:45 PM Description: Ought to be possible to use ConsoleAnnotator implementations to produce rich output from tasks. Project: Jenkins Labels: api Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-26054) FileMonitoringTask based on ProcStarter
Jesse Glick updated JENKINS-26054 FileMonitoringTask based on ProcStarter Change By: Jesse Glick (12/Dec/14 7:47 PM) Labels: api workflow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-26054) FileMonitoringTask based on ProcStarter
Jesse Glick updated JENKINS-26054 FileMonitoringTask based on ProcStarter Change By: Jesse Glick (12/Dec/14 7:48 PM) Labels: api workflow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26055) DurableTaskStep
Jesse Glick created JENKINS-26055 DurableTaskStep Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 12/Dec/14 7:47 PM Description: Should be a generic step to pick any DurableTask. Project: Jenkins Labels: api Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-26056) Workflow build step
Jesse Glick created JENKINS-26056 Workflow build step Issue Type: New Feature Assignee: Unassigned Components: ant-plugin Created: 12/Dec/14 7:49 PM Description: A way to run Ant from a workflow using configured Ant installations and so on. Project: Jenkins Labels: workflow Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26055) DurableTaskStep
Jesse Glick commented on JENKINS-26055 DurableTaskStep Workaround is to use sh/bat and run the tool manually, using tool as needed to install it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26057) Workflow build step for Maven
Jesse Glick created JENKINS-26057 Workflow build step for Maven Issue Type: New Feature Assignee: Unassigned Components: maven-plugin Created: 12/Dec/14 7:51 PM Description: Really belongs in a different plugin as described in https://trello.com/c/ImfSSGkj/4-classic-maven-builder-into-maven-builder-plugin but filing here for the moment. A way to run Maven from a workflow using configured Maven installations and with support for other features such as settings files and console highlighting. Project: Jenkins Labels: workflow Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clone-workspace-scm-plugin] (JENKINS-26058) Implement a tarball-only option for cloning the workspace
Luke Petre created JENKINS-26058 Implement a tarball-only option for cloning the workspace Issue Type: Improvement Assignee: Unassigned Components: clone-workspace-scm-plugin Created: 12/Dec/14 7:53 PM Description: For workspaces that are very large and don't compress well, the overhead of tar+gzip might be frustrating. It would be nice to have the option to only tar the workspace. Project: Jenkins Priority: Minor Reporter: Luke Petre This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [elasticbox-plugin] (JENKINS-25978) Workflow integration
Phong Le commented on JENKINS-25978 Workflow integration We will consider making ElasticBox build steps and post build actions available in the workflow job. This is not only to enable workflow to utilize temporary servers for testing purpose but also to deploy and manage application running on any clouds as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24380) Use build numbers as IDs
Jesse Glick commented on JENKINS-24380 Use build numbers as IDs What if we make new build directory names …and leave old directories intact … Cannot see a straightforward way to make this work. We cannot rely on symlinks because of Windows users. The new code expects timestamp to be persistent, and number to be computed, which clashes with the format expected by older versions of Jenkins. Providing a tool to reverse the migration for anyone who needs to downgrade seems less risky than managing mixed-format records. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clone-workspace-plugin] (JENKINS-26058) Implement a tarball-only option for cloning the workspace
Luke Petre updated JENKINS-26058 Implement a tarball-only option for cloning the workspace Change By: Luke Petre (12/Dec/14 8:51 PM) Component/s: clone-workspace-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-13887) Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build
lacostej closed JENKINS-13887 as Fixed Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build Change By: lacostej (12/Dec/14 9:14 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-13887) Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build
lacostej resolved JENKINS-13887 as Fixed Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build should be released by now. Change By: lacostej (12/Dec/14 9:14 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-19924) Removes previous .ipa files
lacostej
edited a comment on JENKINS-19924
Removes previous .ipa files
Is this still the case ? The project is supposed to be able to multiple IPAs. Can you describe your config a bit more ?
Are you using multiple xcode build steps in one job ? Then yes, this could cause it because we do something like
for (FilePath path : ipaOutputPath.list("*.ipa")) {
path.delete();
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-19924) Removes previous .ipa files
lacostej
commented on JENKINS-19924
Removes previous .ipa files
Is this still the case ? The project is supposed to be able to multiple IPAs. Can you describe your config a bit more ?
Are you using multiple xcode build steps in one job ? Then yes, this could cause it because we do something like
for (FilePath path : ipaOutputPath.list("*.ipa")) {
path.delete();
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [elasticbox-plugin] (JENKINS-25978) Workflow integration
Jesse Glick commented on JENKINS-25978 Workflow integration So for build steps (including post-build actions) you just need to implement SimpleBuildStep. To allow workflow node blocks to run on ElasticBox clouds, possibly nothing is required, but you should not implement EphemeralNode (so the flow can survive a restart of Jenkins), and you may need to use the APIs in the executions package of the durable-task plugin to prevent a slave from being disposed of too early. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-13929) allow to define a fix name for an IPA
lacostej resolved JENKINS-13929 as Fixed allow to define a fix name for an IPA This was implemented a few release ago Change By: lacostej (12/Dec/14 9:30 PM) Status: Open Resolved Assignee: ArnaudHéritier lacostej Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-13929) allow to define a fix name for an IPA
lacostej closed JENKINS-13929 as Fixed allow to define a fix name for an IPA Change By: lacostej (12/Dec/14 9:30 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-24897) Build fails with jenkins XCode Integration Plugin with XCode 6.0.1
lacostej commented on JENKINS-24897 Build fails with jenkins XCode Integration Plugin with XCode 6.0.1 I remember having lots of issues like " Tests/Unity-iPhone Tests-Prefix.pch' has been modified since the precompiled header " until I spent time properly cleaning the xcode temporary files in between Unity upgrades for example. It could also be because of spacing issues in file paths. Could you share your config to see where those are added ? I see some in Unity-iPhone\ Tests for example. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-13772) Produce tokens with Token Macro plugin
lacostej commented on JENKINS-13772 Produce tokens with Token Macro plugin I looked a bit into how this works and here are some implementation links in case someone is interested https://github.com/jenkinsci/ownership-plugin/blob/f1605fceac038aa4aaabf926e98be4f57b9f47b6/src/main/java/com/synopsys/arc/jenkins/plugins/ownership/wrappers/OwnershipTokenMacro.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-18480) String parsing bug in xcode plugin 1.3.3;
lacostej resolved JENKINS-18480 as Fixed String parsing bug in xcode plugin 1.3.3; Change By: lacostej (12/Dec/14 9:39 PM) Status: Open Resolved Assignee: lacostej Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-18480) String parsing bug in xcode plugin 1.3.3;
lacostej closed JENKINS-18480 as Fixed String parsing bug in xcode plugin 1.3.3; Change By: lacostej (12/Dec/14 9:39 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-18480) String parsing bug in xcode plugin 1.3.3;
lacostej commented on JENKINS-18480 String parsing bug in xcode plugin 1.3.3; Closing. I am not aware of quoting issues. Please report if this is still a problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-23447) Sensitive build variables recorded in EnvInjectSavable and displayed in EnvInjectAction
Steven Christou resolved JENKINS-23447 as Fixed Sensitive build variables recorded in EnvInjectSavable and displayed in EnvInjectAction Nicolas De Loof solved it as part of d50c5a Change By: Steven Christou (12/Dec/14 9:42 PM) Status: Open Resolved Assignee: GregoryBoissinot NicolasDeLoof Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-22163) Xcode plugin: Can't use environment variable
lacostej closed JENKINS-22163 as Fixed Xcode plugin: Cant use environment variable Change By: lacostej (12/Dec/14 9:47 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-22163) Xcode plugin: Can't use environment variable
lacostej commented on JENKINS-22163 Xcode plugin: Cant use environment variable I am not sure this is supposed to work: Building in workspace /Users/lacostej/.jenkins/jobs/test_shell_export/workspace [workspace] $ /bin/sh -xe /var/folders/zh/pbp2qp89321_0v_hq8fp_qv4gn/T/hudson8776117682287385802.sh + CVSRTR=toto + export CVSRTR [workspace] $ /bin/sh -xe /var/folders/zh/pbp2qp89321_0v_hq8fp_qv4gn/T/hudson1269574960451974800.sh + echo 'CVSRTR ' CVSRTR So shells are not able to export env. variables to following build steps. I use EnvInject or similar to do this. Closing issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-22163) Xcode plugin: Can't use environment variable
lacostej resolved JENKINS-22163 as Fixed Xcode plugin: Cant use environment variable Change By: lacostej (12/Dec/14 9:47 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-23535) NullPointerException when packaging IPA (Xcode plugin 1.4.2 Jenkins 1.568)
lacostej closed JENKINS-23535 as Fixed NullPointerException when packaging IPA (Xcode plugin 1.4.2 Jenkins 1.568) Change By: lacostej (12/Dec/14 9:52 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-23535) NullPointerException when packaging IPA (Xcode plugin 1.4.2 Jenkins 1.568)
lacostej resolved JENKINS-23535 as Fixed NullPointerException when packaging IPA (Xcode plugin 1.4.2 Jenkins 1.568) problem was caused by provideApplicationVersion being null upon upgrades for older configs. Several fixes where made to avoid NPEs and properly migrate config to newer formats. Closing. Change By: lacostej (12/Dec/14 9:52 PM) Status: Open Resolved Assignee: lacostej Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-12635) packaging ipa doesn´t work if run on a slave
lacostej commented on JENKINS-12635 packaging ipa doesn´t work if run on a slave This is probably related to JENKINS-17457 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-12635) packaging ipa doesn´t work if run on a slave
lacostej closed JENKINS-12635 as Fixed packaging ipa doesn´t work if run on a slave Change By: lacostej (12/Dec/14 9:55 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-12635) packaging ipa doesn´t work if run on a slave
lacostej resolved JENKINS-12635 as Fixed packaging ipa doesn´t work if run on a slave Change By: lacostej (12/Dec/14 9:54 PM) Status: Open Resolved Assignee: ArnaudHéritier lacostej Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-16357) In each Generated Project, show the seed job that created it.
Wisen Tanasa commented on JENKINS-16357 In each Generated Project, show the seed job that created it. Pull request: https://github.com/jenkinsci/job-dsl-plugin/pull/335 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-16356) In each Project, show templates being used
Wisen Tanasa commented on JENKINS-16356 In each Project, show templates being used Pull request: https://github.com/jenkinsci/job-dsl-plugin/pull/335 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16352) Add ability to specify parameters in the crontab
Ed Abshire commented on JENKINS-16352 Add ability to specify parameters in the crontab We are using Jenkins as an orchestration engine to kick off tasks. We have a common task shared across multiple teams that just varies by parameters. For scheduling, this would be really nice for us to be able to let our users schedule their task with the parameters for their tests and have it kick off when they want at a set time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp-plugin] (JENKINS-26059) Expand variables before using conditional
Brantone created JENKINS-26059 Expand variables before using conditional Issue Type: Bug Assignee: Unassigned Components: hockeyapp-plugin Created: 12/Dec/14 11:13 PM Description: A few parts in the code check for a variable being null, then execute some code. However, when using Parameters, the value itself won't be null, but if that parameter then expands to an empty string it would be equivalent of null. For example: In https://github.com/jenkinsci/hockeyapp-plugin/blob/master/src/main/java/hockeyapp/HockeyappRecorder.java#L216 Checking dsymPath for null would return "$SYMBOLEFILES" as not null; however, if a build is parameterized and that value is empty, it would be equivalent of null when expanded on line 217/218 Therefore, should be expanded before checking. Project: Jenkins Priority: Minor Reporter: Brantone This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-26060) Using Jenkins 1.583. Today updated plugins, junit publisher now crashes.
Richard Walker created JENKINS-26060 Using Jenkins 1.583. Today updated plugins, junit publisher now crashes. Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 12/Dec/14 11:45 PM Description: Matrix job, all children "succeed" and then fail when publishing junit report ... BUILD SUCCESSFUL Total time: 21 seconds + exit 0 Recording test results ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception java.lang.NoClassDefFoundError: jenkins/MasterToSlaveFileCallable at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:756) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:90) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:120) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:137) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.ClassNotFoundException: jenkins.MasterToSlaveFileCallable at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1375) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) ... 23 more Environment: Jenkins 1.583 Junit 1.3 Matrix Project 1.4 java version 1.6.0_45 Linux CentOS 5 32-bit Project: Jenkins Labels: plugin jenkins junit crash matrix Priority: Blocker Reporter: Richard Walker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-24887) Workflow support of Copyartifact
Sean Sutherland assigned JENKINS-24887 to Sean Sutherland Workflow support of Copyartifact Change By: Sean Sutherland (13/Dec/14 12:32 AM) Assignee: SeanSutherland This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-24887) Workflow support of Copyartifact
Sean Sutherland assigned JENKINS-24887 to Unassigned Workflow support of Copyartifact Change By: Sean Sutherland (13/Dec/14 12:33 AM) Assignee: SeanSutherland This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-21293) Xcode integration 1.4.2 Generate IPA Failed to build
lacostej resolved JENKINS-21293 as Not A Defect Xcode integration 1.4.2 Generate IPA Failed to build see a3e44e1 Change By: lacostej (13/Dec/14 7:29 AM) Status: Open Resolved Assignee: lacostej Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-21293) Xcode integration 1.4.2 Generate IPA Failed to build
lacostej commented on JENKINS-21293 Xcode integration 1.4.2 Generate IPA Failed to build Yes. This is a user configuration error. I've pushed a commit to display a warning at IPA generation time. It could have been added to the GUI instead / as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
