[JIRA] [groovy-plugin] (JENKINS-26635) Provide Groovy workflow build step
Thomas Goeppel commented on JENKINS-26635 Provide Groovy workflow build step Getting data in, and out of such a Groovy build step should be as easy, and unobstrisive as possible: data in - e.g. env, data out - e.g. map like in Workflow Input step adding jars to the class path should be simple - e.g. cp relative to workspace in Groovy tool configuration 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] [s3-plugin] (JENKINS-27284) Option to not make a build unstable under problem with the S3 pugin
Félix Belzunce Arcos created JENKINS-27284 Option to not make a build unstable under problem with the S3 pugin Issue Type: Bug Assignee: Félix Belzunce Arcos Components: s3-plugin Created: 08/Mar/15 8:59 PM Description: Sometimes S3 publishes fails for various reasons. This causes the whole job to fail. While I care about s3 publish, I don't want the job to fail if s3 fails. An idea might be to add a new checkbox 'Pass always'. If enabled, the job should pass even if S3 publish fails my latest failure from S3 is this 00-00 00:37:28 Publish artifacts to S3 Bucket bucket=qa-splunk-artifacts, file=helmut.log region=us-east-1, upload from slave=false managed=true , server encryption false 00-00 00:37:29 FATAL: Unable to load resource META-INF/services/org.apache.commons.logging.LogFactory 00-00 00:37:29 java.lang.Error: Unable to load resource META-INF/services/org.apache.commons.logging.LogFactory 00-00 00:37:29 at hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:376) 00-00 00:37:29 at java.lang.ClassLoader.getResource(Unknown Source) 00-00 00:37:29 at java.net.URLClassLoader.getResourceAsStream(Unknown Source) 00-00 00:37:29 at org.apache.commons.logging.LogFactory$3.run(LogFactory.java:1280) 00-00 00:37:29 at java.security.AccessController.doPrivileged(Native Method) 00-00 00:37:29 at org.apache.commons.logging.LogFactory.getResourceAsStream(LogFactory.java:1276) 00-00 00:37:29 at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:532) 00-00 00:37:29 at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:657) 00-00 00:37:29 at org.apache.http.impl.conn.DefaultClientConnection.init(DefaultClientConnection.java:75) 00-00 00:37:29 at org.apache.http.impl.conn.DefaultClientConnectionOperator.createConnection(DefaultClientConnectionOperator.java:137) 00-00 00:37:29 at org.apache.http.impl.conn.HttpConnPool$InternalConnFactory.create(HttpConnPool.java:76) 00-00 00:37:29 at org.apache.http.impl.conn.HttpConnPool$InternalConnFactory.create(HttpConnPool.java:67) 00-00 00:37:29 at org.apache.http.pool.AbstractConnPool.getPoolEntryBlocking(AbstractConnPool.java:270) 00-00 00:37:29 at org.apache.http.pool.AbstractConnPool.access$000(AbstractConnPool.java:62) 00-00 00:37:29 at org.apache.http.pool.AbstractConnPool$2.getPoolEntry(AbstractConnPool.java:176) 00-00 00:37:29 at org.apache.http.pool.AbstractConnPool$2.getPoolEntry(AbstractConnPool.java:172) 00-00 00:37:29 at org.apache.http.pool.PoolEntryFuture.get(PoolEntryFuture.java:100) 00-00 00:37:29 at org.apache.http.impl.conn.PoolingClientConnectionManager.leaseConnection(PoolingClientConnectionManager.java:212) 00-00 00:37:29 at org.apache.http.impl.conn.PoolingClientConnectionManager$1.getConnection(PoolingClientConnectionManager.java:199) 00-00 00:37:29 at sun.reflect.GeneratedMethodAccessor435.invoke(Unknown Source) 00-00 00:37:29 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 00-00 00:37:29 at java.lang.reflect.Method.invoke(Unknown Source) 00-00 00:37:29 at com.amazonaws.http.conn.ClientConnectionRequestFactory$Handler.invoke(ClientConnectionRequestFactory.java:70) 00-00 00:37:29 at com.amazonaws.http.conn.$Proxy82.getConnection(Unknown Source) 00-00 00:37:29 at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:456) 00-00 00:37:29 at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906) 00-00 00:37:29 at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805) 00-00 00:37:29 at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:685) 00-00 00:37:29 at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:460) 00-00 00:37:29 at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:295) 00-00 00:37:29 at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3697) 00-00 00:37:29 at com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1434) 00-00 00:37:29 at
[JIRA] [workflow-plugin] (JENKINS-26192) Add support for Grape (@Grab) in workflow scripts
Thomas Goeppel commented on JENKINS-26192 Add support for Grape (@Grab) in workflow scripts CPS was designed for writing build definitions, and I can see why one should avoid turning it into a general data processing language. In my use case, data processing (e.g. communicating with a web service) could as well be done with a beefed-up Groovy build step (- JENKINS-26635) 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] [multiple-scms-plugin] (JENKINS-26303) Not compatible with Subversion plugin 2.5
SCM/JIRA link daemon commented on JENKINS-26303 Not compatible with Subversion plugin 2.5 Code changed in jenkins User: Craig Rodrigues Path: src/main/java/org/jenkinsci/plugins/multiplescms/MultiSCM.java http://jenkins-ci.org/commit/multiple-scms-plugin/1e7d7bd69f923d1a78a9a03a1beb24aab0dcc7e5 Log: Do not add a SCMRevisionState of type MultiSCMRevisionState to the MultiSCMRevisionState variable associated with the overal job. When a MultiSCM.checkout() is done, the list of SCMs is iterated over. For each SCM in the list, we obtain the SCMRevisionState for that SCM and pass it down to the checkout() method for each SCM. For a Subversion checkout, the Subversion plugin downcasts the revision revision state to SVNRevisionState. Without this fix, a revision state of type MultiSCMRevisionState was being passed down into the Subversion plugin. This was causing a ClassCastException to be thrown. FIXED JENKINS-26303 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] [multiple-scms-plugin] (JENKINS-26303) Not compatible with Subversion plugin 2.5
SCM/JIRA link daemon resolved JENKINS-26303 as Fixed Not compatible with Subversion plugin 2.5 Change By: SCM/JIRA link daemon (08/Mar/15 7:15 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] [multiple-scms-plugin] (JENKINS-26734) Subversion Plugin 2.5 is incompatible with Multiple SCM plugin
Craig Rodrigues updated JENKINS-26734 Subversion Plugin 2.5 is incompatible with Multiple SCM plugin Change By: Craig Rodrigues (08/Mar/15 7:50 PM) Component/s: multiple-scms-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] [multiple-scms-plugin] (JENKINS-26734) Subversion Plugin 2.5 is incompatible with Multiple SCM plugin
Craig Rodrigues resolved JENKINS-26734 as Duplicate Subversion Plugin 2.5 is incompatible with Multiple SCM plugin Change By: Craig Rodrigues (08/Mar/15 7:51 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25757) Windows 2003 is an unknown platform
Ross Rowe
commented on JENKINS-25757
Windows 2003 is an unknown platform
The Jenkins plugin uses the results of the Sauce REST API to present the list of platforms available under Sauce (https://saucelabs.com/rest/v1/info/browsers/webdriver), and the platform value that is supplies is a fine-grained value (eg. Windows 2008, Windows 2012, etc). The Platform enum included as part of the Selenium source code is a course-grained value and represents the broader platform which is to be used, and doesn't necessarily have a 1-1 relationship with the available Sauce platforms (eg. for the iOS and Android devices).
The preferred approach to set the platform on the capabilities is to use the platform value directly without converting it, eg.
capabilities.setCapability("platform", System.getenv("SELENIUM_PLATFORM"))
however Selenium 2.44.0 introduced a change whereby the Selenium code would attempt to convert this value into a Platform enum value. This change should've been reverted in Selenium 2.45.0, so the code listed about should now work.
The value for the SELENIUM_PLATFORM environment variable is the same as the 'os' attribute in the SAUCE_ONDEMAND_BROWSERS environment variable, ideally they should have similar names, but at this stage it would be difficult to change their names without impacting multiple users.
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] [audit2db-plugin] (JENKINS-27283) Missing classes directory when audit2db installs
Matt Firtion created JENKINS-27283 Missing classes directory when audit2db installs Issue Type: Bug Assignee: Unassigned Components: audit2db-plugin Created: 08/Mar/15 8:08 PM Description: When installing audit2db through the Update Center or Advanced file upload, the audit2db directory is missing the classes directory under WEB-INF. . ├── css │ ├── print.css │ └── screen.css ├── help │ ├── jdbcDriver.html │ ├── jdbcUrl.html │ ├── jndiDatasource.html │ └── jobHistoryJobName.html ├── META-INF │ ├── MANIFEST.MF │ └── maven │ └── org.jenkins-ci.plugins │ └── audit2db │ ├── pom.properties │ └── pom.xml └── WEB-INF ├── lib │ ├── antlr-2.7.6.jar │ ├── aopalliance-1.0.jar │ ├── c3p0-0.9.1.2.jar │ ├── cglib-nodep-2.2.jar │ ├── classes.jar │ ├── commons-collections-3.1.jar │ ├── commons-logging-1.1.1.jar │ ├── hibernate-annotations-3.5.6-Final.jar │ ├── hibernate-c3p0-3.5.6-Final.jar │ ├── hibernate-commons-annotations-3.2.0.Final.jar │ ├── hibernate-core-3.5.6-Final.jar │ ├── hibernate-jpa-2.0-api-1.0.0.Final.jar │ ├── javassist-3.8.0.GA.jar │ ├── jta-1.1.jar │ ├── spring-aop-2.5.jar │ ├── spring-asm-3.1.2.RELEASE.jar │ ├── spring-beans-3.1.2.RELEASE.jar │ ├── spring-context-3.1.2.RELEASE.jar │ ├── spring-core-3.1.2.RELEASE.jar │ ├── spring-_expression_-3.1.2.RELEASE.jar │ ├── spring-jdbc-3.1.2.RELEASE.jar │ ├── spring-orm-3.1.2.RELEASE.jar │ └── spring-tx-3.1.2.RELEASE.jar └── licenses.xml Environment: Jenkins v1.580.3 Standalone Install - Tomcat 7 RHEL 6.6 Oracle JDK 1.7.0_75 Project: Jenkins Priority: Blocker Reporter: Matt Firtion 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-26723) Show displayName in build remote API
Patrik Boström resolved JENKINS-26723 as Fixed Show displayName in build remote API Change By: Patrik Boström (08/Mar/15 9:06 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] [github-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins
Alexandre Zia created JENKINS-27282 Github Webhook not working after upgrade Jenkins and plugins Issue Type: Bug Assignee: Unassigned Components: github-plugin Created: 08/Mar/15 7:13 PM Description: When github sends a webhook to trigger a build in Jenkins, the Job does not start. I've already downgraded Jenkins and github plugin back to original versions but the issue persists. I've also wiped the workspace and started an initial build manually, and the issue persists Adding the logger: "com.cloudbees.jenkins.GitHubWebHook" I can see this stacktrace: Mar 08, 2015 6:29:57 PM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Received POST for https://github.com/MyCompany/MyRepository Mar 08, 2015 6:29:57 PM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Poked MyJob Mar 08, 2015 6:29:57 PM SEVERE com.cloudbees.jenkins.GitHubPushTrigger$1 runPolling Failed to record SCM polling java.lang.NullPointerException at org.jenkinsci.plugins.envinject.EnvInjectPluginAction$1.transformEntry(EnvInjectPluginAction.java:25) at org.jenkinsci.plugins.envinject.EnvInjectPluginAction$1.transformEntry(EnvInjectPluginAction.java:23) at com.google.common.collect.Maps$TransformedEntriesMap$1$1.apply(Maps.java:1218) at com.google.common.collect.Maps$TransformedEntriesMap$1$1.apply(Maps.java:1216) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at java.util.AbstractMap.putAll(AbstractMap.java:272) at java.util.TreeMap.putAll(TreeMap.java:321) at org.jenkinsci.plugins.envinject.EnvInjectVarList.init(EnvInjectVarList.java:26) at org.jenkinsci.plugins.envinject.EnvInjectPluginAction.getTarget(EnvInjectPluginAction.java:22) at org.jenkinsci.plugins.envinject.EnvInjectPluginAction.buildEnvVars(EnvInjectPluginAction.java:31) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:929) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:564) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:526) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:380) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1446) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at com.cloudbees.jenkins.GitHubPushTrigger$1.runPolling(GitHubPushTrigger.java:81) at com.cloudbees.jenkins.GitHubPushTrigger$1.run(GitHubPushTrigger.java:106) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679)Mar 08, 2015 6:29:57 PM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Environment: Latest Jenkins 1.601 but hte issue had appeared in 1.600 Project: Jenkins Priority: Major Reporter: Alexandre Zia 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.
[JIRA] [groovy-plugin] (JENKINS-26635) Provide Groovy workflow build step
Thomas Goeppel edited a comment on JENKINS-26635 Provide Groovy workflow build step Getting data in, and out of such a Groovy build step should be as easy, and unobstrisive as possible: data in - e.g. env, data out - e.g. map like in Workflow Input step adding jars to the class path should be simple - e.g. cp relative to workspace in Groovy tool configuration "data out" is maybe the same as JENKINS-26133 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] [multiple-scms-plugin] (JENKINS-25131) Multiple SCMs Plugin doesn't track multiple Git Repo SHA1
SCM/JIRA link daemon resolved JENKINS-25131 as Fixed Multiple SCMs Plugin doesnt track multiple Git Repo SHA1 Change By: SCM/JIRA link daemon (08/Mar/15 8:21 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] [multiple-scms-plugin] (JENKINS-25131) Multiple SCMs Plugin doesn't track multiple Git Repo SHA1
SCM/JIRA link daemon commented on JENKINS-25131 Multiple SCMs Plugin doesnt track multiple Git Repo SHA1 Code changed in jenkins User: JACOB R. GARCOWSKI Path: src/main/java/org/jenkinsci/plugins/multiplescms/MultiSCM.java src/main/java/org/jenkinsci/plugins/multiplescms/MultiSCMChangeLogParser.java http://jenkins-ci.org/commit/multiple-scms-plugin/cfe435be85573a90423a760beacbf405ed40055b Log: Changing to key change parsers off of SCM.getKey() instead of getType(). This change is required since different ChangeLogParsers are needed when multiple git SCMs are used, since each goes to a different repository. Tested only with git, but should not break other SCMs because of how getKey() is defined in the Jenkins API. FIXED JENKINS-25131 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] [s3-plugin] (JENKINS-27284) Option to not make a build unstable under problem with the S3 pugin
Félix Belzunce Arcos
updated JENKINS-27284
Option to not make a build unstable under problem with the S3 pugin
Change By:
Félix Belzunce Arcos
(08/Mar/15 9:00 PM)
Issue Type:
Bug
Improvement
Description:
SometimesS3publishesfailsforvariousreasons.Thiscausesthewholejobtofail.WhileIcareabouts3publish,Idontwantthejobtofailifs3fails.AnideamightbetoaddanewcheckboxPassalways.Ifenabled,thejobshouldpassevenifS3publishfailsmylatestfailurefromS3isthis{noformat}00-:37:28PublishartifactstoS3Bucketbucket=qa-
splunk
x
-artifacts,file=
helmut
xxx
[JIRA] [ec2-plugin] (JENKINS-27281) Provide more control over EC2 instance spawn rate
Mark Brown created JENKINS-27281 Provide more control over EC2 instance spawn rate Issue Type: New Feature Assignee: Francis Upton Components: ec2-plugin Created: 08/Mar/15 6:43 PM Description: Currently the EC2 plugin attempts to create one EC2 slave per job in the queue with some small degree of ramp up (at least in so far as I can tell) - typically on the first poll one or two slaves are started, on the second as many slaves as there are builds are started. It would be very nice to be able to control the rate at which new slaves are created so that there is more chance to use one EC2 slave for multiple builds. My use case is that I'm doing Linux kernel build jobs over a range of configurations, some of which take much longer to build than others to the point where a small number of additional slaves over the quantity needed to do the long running jobs can complete the work required in the time taken for the slow configurations. With the current algorithm the plugin will generally start as many nodes as there are builds which results in greater costs. With less aggressive creation of slaves this could be mitigated for no loss in overall throughput. I could limit the total number of slaves but this would mean that while individual jobs would run more efficiently the EC2 plugin would not be able to add extra capacity if multiple jobs are scheduled at the same time (as is quite common). Project: Jenkins Priority: Minor Reporter: Mark Brown 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-27182) Allow to test Job DSL scripts (simulation mode)
Daniel Spilker commented on JENKINS-27182 Allow to test Job DSL scripts (simulation mode) Please have a look at the job-dsl-gradle-example. It shows how to set up a Gradle build for Job DSL scripts. That allows to compile and test any changes before committing them. It's also possible to use a Gradle build step before the "Process Job DSLs" step in a seed job to run any tests before updating the jobs and views. And the pull request builder can be configured to just execute the Gradle step to run the tests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-21561) GIT Plugin 2.0.1 doesn't work with Jenkins Multiple SCM .3
Craig Rodrigues resolved JENKINS-21561 as Cannot Reproduce GIT Plugin 2.0.1 doesnt work with Jenkins Multiple SCM .3 I tested the problem, it no longer seems to occur with Git plugin 2.3.5 and Multiple SCMS plugin 0.4. Change By: Craig Rodrigues (08/Mar/15 7:34 PM) Status: Open Resolved Assignee: NicolasDeLoof CraigRodrigues 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] [audit2db-plugin] (JENKINS-27283) Missing classes directory when audit2db installs
Matt Firtion updated JENKINS-27283 Missing classes directory when audit2db installs Change By: Matt Firtion (08/Mar/15 8:18 PM) Environment: Jenkinsv1.580.3StandaloneInstall-Tomcat7RHEL6.6OracleJDK1.7.0_75 audit2dbversion0.5 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-combinations-parameter-plugin] (JENKINS-23609) Successful and Failed link in matrix-combinations-parameter do not work
michele hallak-stamler commented on JENKINS-23609 Successful and Failed link in matrix-combinations-parameter do not work Is there some workaround to solve this 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] [workflow-plugin] (JENKINS-26692) build step should allow specification of custom delay
SCM/JIRA link daemon
commented on JENKINS-26692
build step should allow specification of custom delay
Code changed in jenkins
User: tfennelly
Path:
CHANGES.md
aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/WorkspaceStepTest.java
cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/help-script.html
cps/src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStepExecution.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep/config.jelly
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep/help-dir.html
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/config.jelly
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-quietPeriod.html
support/src/test/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepTest.java
http://jenkins-ci.org/commit/workflow-plugin/772063078e09d19adb881f4c5d52188c0ba36620
Log:
Merge branch 'master' into JENKINS-26122
master:
JENKINS-27145 Noting #75 in changelog.
Updating list of unavailable variables (again ).
FIXED JENKINS-26692 Added BuildTriggerStep.quietPeriod.
@tfennelly requests more descriptive variable names.
Needed to update a test as well.
FIXED JENKINS-26072 Added WorkspaceStep.dir.
Updating list of unavailable variables.
Linking to environment variable (${rootURL}/env-vars.html) in the workflow script help page.
Conflicts:
CHANGES.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-26122) Prepend thread name to output
SCM/JIRA link daemon commented on JENKINS-26122 Prepend thread name to output Code changed in jenkins User: tfennelly Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/block.jelly http://jenkins-ci.org/commit/workflow-plugin/a5c5bf6fee6a306371c0b5c87f5e35a356f8fa85 Log: Merge branch 'master' into JENKINS-26122 master: Always produce unique element and function names. Avoids a bug when switching between CpsFlowDefinition and CpsScmFlowDefinition. Allow the location of the element holding Snippetizer to be passed in. Compare: https://github.com/jenkinsci/workflow-plugin/compare/bb6a526703f3...a5c5bf6fee6a 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-27145) Advertise available environment variables
SCM/JIRA link daemon
commented on JENKINS-27145
Advertise available environment variables
Code changed in jenkins
User: tfennelly
Path:
CHANGES.md
aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/WorkspaceStepTest.java
cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/help-script.html
cps/src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStepExecution.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep/config.jelly
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep/help-dir.html
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/config.jelly
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-quietPeriod.html
support/src/test/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepTest.java
http://jenkins-ci.org/commit/workflow-plugin/772063078e09d19adb881f4c5d52188c0ba36620
Log:
Merge branch 'master' into JENKINS-26122
master:
JENKINS-27145 Noting #75 in changelog.
Updating list of unavailable variables (again ).
FIXED JENKINS-26692 Added BuildTriggerStep.quietPeriod.
@tfennelly requests more descriptive variable names.
Needed to update a test as well.
FIXED JENKINS-26072 Added WorkspaceStep.dir.
Updating list of unavailable variables.
Linking to environment variable (${rootURL}/env-vars.html) in the workflow script help page.
Conflicts:
CHANGES.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-26072) Specify alternate path to lock in WorkspaceStep
SCM/JIRA link daemon
commented on JENKINS-26072
Specify alternate path to lock in WorkspaceStep
Code changed in jenkins
User: tfennelly
Path:
CHANGES.md
aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/WorkspaceStepTest.java
cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/help-script.html
cps/src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStepExecution.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep/config.jelly
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep/help-dir.html
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/config.jelly
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-quietPeriod.html
support/src/test/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepTest.java
http://jenkins-ci.org/commit/workflow-plugin/772063078e09d19adb881f4c5d52188c0ba36620
Log:
Merge branch 'master' into JENKINS-26122
master:
JENKINS-27145 Noting #75 in changelog.
Updating list of unavailable variables (again ).
FIXED JENKINS-26692 Added BuildTriggerStep.quietPeriod.
@tfennelly requests more descriptive variable names.
Needed to update a test as well.
FIXED JENKINS-26072 Added WorkspaceStep.dir.
Updating list of unavailable variables.
Linking to environment variable (${rootURL}/env-vars.html) in the workflow script help page.
Conflicts:
CHANGES.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-26122) Prepend thread name to output
SCM/JIRA link daemon
commented on JENKINS-26122
Prepend thread name to output
Code changed in jenkins
User: tfennelly
Path:
CHANGES.md
aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/WorkspaceStepTest.java
cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/help-script.html
cps/src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStepExecution.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep.java
support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep/config.jelly
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/WorkspaceStep/help-dir.html
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/config.jelly
support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-quietPeriod.html
support/src/test/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepTest.java
http://jenkins-ci.org/commit/workflow-plugin/772063078e09d19adb881f4c5d52188c0ba36620
Log:
Merge branch 'master' into JENKINS-26122
master:
JENKINS-27145 Noting #75 in changelog.
Updating list of unavailable variables (again ).
FIXED JENKINS-26692 Added BuildTriggerStep.quietPeriod.
@tfennelly requests more descriptive variable names.
Needed to update a test as well.
FIXED JENKINS-26072 Added WorkspaceStep.dir.
Updating list of unavailable variables.
Linking to environment variable (${rootURL}/env-vars.html) in the workflow script help page.
Conflicts:
CHANGES.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-26122) Prepend thread name to output
SCM/JIRA link daemon commented on JENKINS-26122 Prepend thread name to output Code changed in jenkins User: tfennelly Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/parallel/ParallelStepTest.java api/src/main/java/org/jenkinsci/plugins/workflow/actions/BodyExecutionLabelAction.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/steps/ParallelStep.java job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-plugin/26c0b445561881be1296309e19a6ed5eb6b8e0ea Log: FIXED JENKINS-26122 Prepend parallel step execution logs with the branch label 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-26122) Prepend thread name to output
SCM/JIRA link daemon resolved JENKINS-26122 as Fixed Prepend thread name to output Change By: SCM/JIRA link daemon (08/Mar/15 10:09 AM) 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] [subversion-plugin] (JENKINS-25538) Add Phabricator as Repository Browser
aristedes
commented on JENKINS-25538
Add Phabricator as Repository Browser
To assist with the development of this, here is the pattern:
https?://${baseURL}/r${repoCode}${commitNumber}
${repoCode} is a one character code defined for the repository. It has the letter "r" before it. Really, it could all be part of the baseURL like this:
baseURL = https://phabricator.acme.com/rC
and then we just stick the commit number at the end.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error Please login prior to push after publishing the image
Michael Neale commented on JENKINS-27229 Docker publish plugin throws error Please login prior to push after publishing the image can you share more of your config for the job and plugin? that looks lik eit is missing the username in the settings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-27285) Can not Get Jenkins environment Correctly with Promote Builds Plugin
shans zoe created JENKINS-27285 Can not Get Jenkins environment Correctly with Promote Builds Plugin Issue Type: Bug Assignee: Unassigned Attachments: promote_config1.jpg, promote_config2.jpg, promote_result.jpg Components: promoted-builds-plugin Created: 09/Mar/15 3:31 AM Description: I just run execute shell in zhe Promoted Builds Plugin，and there are some Jenkins environment variables in the commands，But I get nothing with the environment variables. Environment: Jenkins： 1.563 Platform： Windows Server 2003 with SP2 Promoted Builds Plugin：2.19 Project: Jenkins Priority: Critical Reporter: shans zoe 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] [s3-plugin] (JENKINS-26903) S3 plugin missing http jars
Ross Golder commented on JENKINS-26903 S3 plugin missing http jars I also had to copy the jars from the lib folder of httpclient-4.4 and httpcore-4.4 to the S3 plugin (/var/lib/jenkins/plugins/s3/WEB-INF/lib/) and restart Jenkins for this to work. 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] [accelerated-build-now-plugin] (JENKINS-27286) Jual Obat Bius 085600025909
obat Asli created JENKINS-27286 Jual Obat Bius 085600025909 Issue Type: Bug Assignee: obat Asli Attachments: Liquid Sex.jpg Components: accelerated-build-now-plugin Created: 09/Mar/15 4:31 AM Description: jual obat bius Environment: obat bius Project: Jenkins Labels: jual obat bius murah, Priority: Minor Reporter: obat Asli 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] [s3-plugin] (JENKINS-26903) S3 plugin missing http jars
Ross Golder commented on JENKINS-26903 S3 plugin missing http jars I've sponsored this issue with a few mBTC. Let's get this fixed quickly before any more devops tears are shed 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-26544) Select All icon in configuration page looks image not found icon
Chintan Patel updated JENKINS-26544 Select All icon in configuration page looks image not found icon As per Daniel Beck's comment the icon should look like attached edit-select-all icon. Change By: Chintan Patel (09/Mar/15 5:15 AM) Attachment: edit-select-all.png 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-21225) Configuration Slicing for Editable Email Notification not working anymore with latest versions
SCM/JIRA link daemon commented on JENKINS-21225 Configuration Slicing for Editable Email Notification not working anymore with latest versions Code changed in jenkins User: ninian Path: pom.xml src/main/java/configurationslicing/email/ExtEmailSlicer.java src/main/java/configurationslicing/email/ProjectHandler.java src/test/java/configurationslicing/EmailSlicerTest.java http://jenkins-ci.org/commit/configurationslicing-plugin/e454609618fb7400a6a092080185ee9131eb7b69 Log: Merge pull request #15 from ninian/master PR for JENKINS-21225 Compare: https://github.com/jenkinsci/configurationslicing-plugin/compare/c0d1e56794ac...e454609618fb 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] [digitalocean-plugin] (JENKINS-27279) Archived DigitalOcean containers, not starting with jenkins are taken as container
Andreas Pieber started work on JENKINS-27279 Archived DigitalOcean containers, not starting with jenkins are taken as container Change By: Andreas Pieber (08/Mar/15 11:36 AM) Status: Open InProgress 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] [digitalocean-plugin] (JENKINS-27280) Cant start multiple DigitalOcean Maschines
Andreas Pieber started work on JENKINS-27280 Cant start multiple DigitalOcean Maschines Change By: Andreas Pieber (08/Mar/15 11:36 AM) Status: Open InProgress 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 commented on JENKINS-26050 Workflow integration https://github.com/jenkinsci/build-token-root-plugin/commit/e859e2f1cb51b203f8e13932f76ac0a69b2e75e5 may be helpful as an example of ParameterizedJobMixIn usage. 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-26085) Credentials support for git step
Jesse Glick reopened JENKINS-26085 Credentials support for git step Change By: Jesse Glick (08/Mar/15 12:49 PM) Resolution: Fixed Status: Resolved Reopened 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-26085) Credentials support for git step
Jesse Glick started work on JENKINS-26085 Credentials support for git step Change By: Jesse Glick (08/Mar/15 12:49 PM) Status: Open InProgress 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-26085) Credentials support for git step
Jesse Glick updated JENKINS-26085 Credentials support for git step Change By: Jesse Glick (08/Mar/15 12:49 PM) Status: Reopened Open 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-21225) Configuration Slicing for Editable Email Notification not working anymore with latest versions
SCM/JIRA link daemon resolved JENKINS-21225 as Fixed Configuration Slicing for Editable Email Notification not working anymore with latest versions Change By: SCM/JIRA link daemon (08/Mar/15 10:48 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing-plugin] (JENKINS-21225) Configuration Slicing for Editable Email Notification not working anymore with latest versions
SCM/JIRA link daemon commented on JENKINS-21225 Configuration Slicing for Editable Email Notification not working anymore with latest versions Code changed in jenkins User: ninian Path: pom.xml src/main/java/configurationslicing/email/ExtEmailSlicer.java src/main/java/configurationslicing/email/ProjectHandler.java src/test/java/configurationslicing/EmailSlicerTest.java http://jenkins-ci.org/commit/configurationslicing-plugin/68c4a9704b8a9ce4ea630a9bee605ea8638f69fb Log: FIXED JENKINS-21225 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-26121) Input step should maintain audit record
SCM/JIRA link daemon commented on JENKINS-26121 Input step should maintain audit record Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/input/InputStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/ApproverAction.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/InputStepExecution.java support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/input/ApproverAction/summary.jelly support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/input/ApproverAction/summary.properties http://jenkins-ci.org/commit/workflow-plugin/f88042c300e8639dc8e51fa38f989e94638c4ec1 Log: Merge pull request #47 from varmenise/JENKINS-26121 JENKINS-26121 Approver Logged Compare: https://github.com/jenkinsci/workflow-plugin/compare/a5c5bf6fee6a...f88042c300e8 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-26121) Input step should maintain audit record
Jesse Glick resolved JENKINS-26121 as Fixed Input step should maintain audit record Change By: Jesse Glick (08/Mar/15 12:28 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] [workflow-plugin] (JENKINS-26121) Input step should maintain audit record
SCM/JIRA link daemon commented on JENKINS-26121 Input step should maintain audit record Code changed in jenkins User: Valentina Armenise Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/input/InputStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/ApproverAction.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/InputStepExecution.java support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/input/ApproverAction/summary.jelly support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/input/ApproverAction/summary.properties http://jenkins-ci.org/commit/workflow-plugin/36571033f4ec39bd107cd492875607b7f59e1237 Log: JENKINS-26121 - Approver Logged 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] [digitalocean-plugin] (JENKINS-27280) Cant start multiple DigitalOcean Maschines
Andreas Pieber created JENKINS-27280 Cant start multiple DigitalOcean Maschines Issue Type: Bug Assignee: Andreas Pieber Components: digitalocean-plugin Created: 08/Mar/15 11:21 AM Description: It's not possible to start more than one digital ocean container at once. Project: Jenkins Priority: Minor Reporter: Andreas Pieber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
SCM/JIRA link daemon commented on JENKINS-26693 Build token root can not start Workflow plugin jobs Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/build_token_root/BuildRootAction.java src/test/java/org/jenkinsci/plugins/build_token_root/BuildRootActionTest.java http://jenkins-ci.org/commit/build-token-root-plugin/e859e2f1cb51b203f8e13932f76ac0a69b2e75e5 Log: FIXED JENKINS-26693 Support triggering workflows. 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-26085) Credentials support for git step
Jesse Glick commented on JENKINS-26085 Credentials support for git step Anders Hammar JENKINS-27275 tracks the analogous change for the svn 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] [envinject-plugin] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
Oleg Nenashev resolved JENKINS-19852 as Fixed NPE during submission of EnvInject JobProperty configurations I've released the new plugin version. It should become available soon. Closing the issue again Change By: Oleg Nenashev (08/Mar/15 2:09 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] [digitalocean-plugin] (JENKINS-26352) Cannot create Jenkins slaves
Andreas Pieber resolved JENKINS-26352 as Fixed Cannot create Jenkins slaves Basically resolved. Just waiting for someone to merge my fix Change By: Andreas Pieber (08/Mar/15 11:11 AM) 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] [digitalocean-plugin] (JENKINS-27279) Archived DigitalOcean containers, not starting with jenkins are taken as container
Andreas Pieber created JENKINS-27279 Archived DigitalOcean containers, not starting with jenkins are taken as container Issue Type: Bug Assignee: Andreas Pieber Components: digitalocean-plugin Created: 08/Mar/15 11:13 AM Description: In fact it's a pretty bad idea to take any contaienr for building software. Basically the better idea is to simply create a new one. Jenkins does remember the original container on reboot so the risk of loosing container link is pretty small anyhow. Alternatively is a feature to create container from snapshots definitely the better solution. Project: Jenkins Priority: Minor Reporter: Andreas Pieber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
SCM/JIRA link daemon commented on JENKINS-26693 Build token root can not start Workflow plugin jobs Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/build_token_root/BuildRootAction.java src/test/java/org/jenkinsci/plugins/build_token_root/BuildRootActionTest.java http://jenkins-ci.org/commit/build-token-root-plugin/8dff08594ff5039ca59eadea74c5d7bb3bc0ea83 Log: Merge pull request #6 from jglick/workflow-JENKINS-26693 JENKINS-26693 Workflow support Compare: https://github.com/jenkinsci/build-token-root-plugin/compare/52d8993385a2...8dff08594ff5 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-26121) Input step should maintain audit record
SCM/JIRA link daemon commented on JENKINS-26121 Input step should maintain audit record Code changed in jenkins User: Jesse Glick Path: CHANGES.md http://jenkins-ci.org/commit/workflow-plugin/f2593795afcbf9908f52adca694f4c58b2387b5b Log: JENKINS-26121 Noting merge of #47. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
SCM/JIRA link daemon resolved JENKINS-26693 as Fixed Build token root can not start Workflow plugin jobs Change By: SCM/JIRA link daemon (08/Mar/15 12:32 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] [build-token-root-plugin] (JENKINS-26693) Build token root can not start Workflow plugin jobs
SCM/JIRA link daemon commented on JENKINS-26693 Build token root can not start Workflow plugin jobs Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/64be5ce6dd7b022c41f94002c52190a185ce309b Log: JENKINS-26693 Noting. 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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Andrew Sumner edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Is there any reason the the update center in Jenkins doesn't find the 2.5 release? It does find 2.4.5 Running latest LTS Jenkins ver. 1.565.3. 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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Andrew Sumner commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Is there any reason the the update center in Jenkins doesn't find the 2.5 release? It does find 2.5.4. Running latest LTS Jenkins ver. 1.565.3. 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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Daniel Beck commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Andrew Sumner: 2.5 requires Jenkins 1.568, as you can see on the plugin's wiki page right at the top. 1.565.3 hasn't been "latest LTS" in months, see http://jenkins-ci.org/changelog-stable the stable update centers just don't offer core upgrades to newer baselines. Please ask your next unrelated question on IRC or the jenkinsci-users mailing list. 200 people are notified about every comment created or edited in this issue, so let's keep this on topic (and yes, I realize my comment sends another notification, but I expect that someone would have responded anyway). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22323) job dsl object creation dialect change
Daniel Spilker closed JENKINS-22323 as Fixed job dsl object creation dialect change Change By: Daniel Spilker (08/Mar/15 2:59 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] [job-dsl-plugin] (JENKINS-27063) ExtendedEmail Configure Block Behavior
Daniel Spilker closed JENKINS-27063 as Fixed ExtendedEmail Configure Block Behavior Change By: Daniel Spilker (08/Mar/15 2:59 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] [job-dsl-plugin] (JENKINS-17513) For SVN only one workspaceupdater is supported
Daniel Spilker closed JENKINS-17513 as Fixed For SVN only one workspaceupdater is supported Change By: Daniel Spilker (08/Mar/15 2:58 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] [job-dsl-plugin] (JENKINS-26424) Abort build option isn't supported for build timeout plugin
Daniel Spilker closed JENKINS-26424 as Fixed Abort build option isnt supported for build timeout plugin Change By: Daniel Spilker (08/Mar/15 2:59 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] [job-dsl-plugin] (JENKINS-19979) DSL plugin 1.18 causes NPEs when saving or creating new jobs.
Daniel Spilker closed JENKINS-19979 as Wont Fix DSL plugin 1.18 causes NPEs when saving or creating new jobs. Change By: Daniel Spilker (08/Mar/15 2:58 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] [job-dsl-plugin] (JENKINS-26796) Add custom configuration support to MultiJob job
Daniel Spilker closed JENKINS-26796 as Fixed Add custom configuration support to MultiJob job Change By: Daniel Spilker (08/Mar/15 2:59 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] [job-dsl-plugin] (JENKINS-26849) Running DSL scripts from cloned repository has the wrong workspace dir
Daniel Spilker closed JENKINS-26849 as Not A Defect Running DSL scripts from cloned repository has the wrong workspace dir Change By: Daniel Spilker (08/Mar/15 2:58 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] [job-dsl-plugin] (JENKINS-24985) Perforce configVersion is not set
Daniel Spilker closed JENKINS-24985 as Not A Defect Perforce configVersion is not set Change By: Daniel Spilker (08/Mar/15 2:59 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] [job-dsl-plugin] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Daniel Spilker closed JENKINS-17222 as Fixed Add ability to specify more than one location when using the svn method Change By: Daniel Spilker (08/Mar/15 2:59 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] [job-dsl-plugin] (JENKINS-24943) add groovy() method to buildWrappers = environmentVariables
Daniel Spilker closed JENKINS-24943 as Fixed add groovy() method to buildWrappers = environmentVariables Change By: Daniel Spilker (08/Mar/15 3:00 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] [job-dsl-plugin] (JENKINS-26853) Add support for Custom Tools Plugin
Daniel Spilker closed JENKINS-26853 as Fixed Add support for Custom Tools Plugin Change By: Daniel Spilker (08/Mar/15 3:00 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] [job-dsl-plugin] (JENKINS-26826) JobDSL plugin doesn't support Categorized Jobs Views
Daniel Spilker closed JENKINS-26826 as Duplicate JobDSL plugin doesnt support Categorized Jobs Views Change By: Daniel Spilker (08/Mar/15 2:59 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] [core] (JENKINS-27268) dumb slave?
luke pao commented on JENKINS-27268 dumb slave? Excellent reference! Would be great to see that kind of change here. 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-26544) Select All icon in configuration page looks image not found icon
Chintan Patel commented on JENKINS-26544 Select All icon in configuration page looks image not found icon It is a toggle button. How about ? 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-26544) Select All icon in configuration page looks image not found icon
Naoki Ishihara commented on JENKINS-26544 Select All icon in configuration page looks image not found icon I like both. They are much better than the current one. 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.
