[JIRA] (JENKINS-48562) Inline Environment Variables not replaced in config file
Title: Message Title
Dominik Bartholdi commented on JENKINS-48562
Re: Inline Environment Variables not replaced in config file
thanks Andrew Bayer! I now tried the following: node{ withEnv(['dbName = "test-$\{env.BUILD_NUMBER}"', 'X_SITENAME = "HELLO"', 'X_DB_USER = "mp"', 'DOMAIN_NAME = "https://www.example.com"']) { configFileProvider([configFile(fileId: 'settings_php', replaceTokens: true, targetLocation: "$\{dbName}/www/local.settings.php")]) { sh "cat ${env.dbName}/www/local.settings.php" } } } node{ withEnv(['dbName = "test-$\{env.BUILD_NUMBER}"', 'X_SITENAME = "HELLO"', 'X_DB_USER = "mp"', 'DOMAIN_NAME = "https://www.example.com"']) { configFileProvider([configFile(fileId: 'settings_php', replaceTokens: true, targetLocation: "$\{dbName}/www/local.settings.php")]) { sh "cat ${dbName}/www/local.settings.php" } } } ...unfortunate it did not work - it already fails at this: sh "cat ${env.dbName}/www/local.settings.php" because it can't find "dbName" tested on:
jenkins 2.73.4.1 (DEV@cloud)
pipeline 2.4
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48562) Inline Environment Variables not replaced in config file
Title: Message Title
Dominik Bartholdi edited a comment on JENKINS-48562
Re: Inline Environment Variables not replaced in config file
thanks [~abayer]!I now tried the following: {code:java} node \ { withEnv(['dbName = "test-$\{env.BUILD_NUMBER}"', 'X_SITENAME = "HELLO"', 'X_DB_USER = "mp"', 'DOMAIN_NAME = "https://www.example.com"']) \ { configFileProvider([configFile(fileId: 'settings_php', replaceTokens: true, targetLocation: "$\{dbName}/www/local.settings.php")]) \ { sh "cat $ \ {env.dbName}/www/local.settings.php" } }} {code} {code:java} node \ { withEnv(['dbName = "test-$\{env.BUILD_NUMBER}"', 'X_SITENAME = "HELLO"', 'X_DB_USER = "mp"', 'DOMAIN_NAME = "https://www.example.com"']) \ { configFileProvider([configFile(fileId: 'settings_php', replaceTokens: true, targetLocation: "$\{dbName}/www/local.settings.php")]) \ { sh "cat $ \ {dbName}/www/local.settings.php" } }} {code} ...unfortunate it did not work - it already fails at this:sh "cat $\{env.dbName}/www/local.settings.php"because it can't find "dbName"tested on: * jenkins 2.73.4.1 (DEV@cloud) * pipeline 2.4
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50044) Run a task on node x or node y
Title: Message Title Dominik Bartholdi assigned an issue to Andrew Bayer Jenkins / JENKINS-50044 Run a task on node x or node y Change By: Dominik Bartholdi Component/s: pipeline-model-definition-plugin Component/s: nodelabelparameter-plugin Assignee: Dominik Bartholdi Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40803) Endless Loop when "provisoning config files..." when run from a build promotion
Title: Message Title Dominik Bartholdi updated JENKINS-40803 Jenkins / JENKINS-40803 Endless Loop when "provisoning config files..." when run from a build promotion Change By: Dominik Bartholdi Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47502) Alphabetical Sort by Name Broken
Title: Message Title Dominik Bartholdi commented on JENKINS-47502 Re: Alphabetical Sort by Name Broken released with 1.8 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40803) Endless Loop when "provisoning config files..." when run from a build promotion
Title: Message Title Dominik Bartholdi commented on JENKINS-40803 Re: Endless Loop when "provisoning config files..." when run from a build promotion released with 1.8 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50563) support declarative pipeline parameter definition
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-50563 support declarative pipeline parameter definition Issue Type: New Feature Assignee: Gesh Markov Components: maven-metadata-plugin Created: 2018-04-04 08:09 Priority: Minor Reporter: Dominik Bartholdi It would be very helpful to be able to define a maven-metadata parameter in declarative pipeline as described here: https://jenkins.io/doc/book/pipeline/syntax/#parameters I know I can do something similar with 'input', but it is not quite the same, as one has to wait for the pipeline to be running. Also I did not find any docu except this commit: https://github.com/jenkinsci/maven-metadata-plugin/commit/a74b2d65824d13f76e175c406983f104390854a0 Add Comment
[JIRA] (JENKINS-50563) support declarative pipeline parameter definition
Title: Message Title Dominik Bartholdi assigned an issue to Marc Rohlfs Jenkins / JENKINS-50563 support declarative pipeline parameter definition Change By: Dominik Bartholdi Assignee: Gesh Markov Marc Rohlfs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50563) support declarative pipeline parameter definition
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-50563 support declarative pipeline parameter definition Change By: Dominik Bartholdi It would be very helpful to be able to define a maven-metadata parameter in declarative pipeline as described here:[https://jenkins.io/doc/book/pipeline/syntax/#parameters] I know I can do something similar with 'input', but it is not quite the same, as one has to wait for the pipeline to be running and the parameter is not visible in the job configuration . Also I did not find any docu except this commit: [https://github.com/jenkinsci/maven-metadata-plugin/commit/a74b2d65824d13f76e175c406983f104390854a0] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.go
[JIRA] (JENKINS-50622) when condition not correctly discovering branch
Title: Message Title
Dominik Bartholdi updated an issue
Jenkins / JENKINS-50622
when condition not correctly discovering branch
Change By:
Dominik Bartholdi
I created a new pipeline job and defined "Pipeline script from SCM" using Git: * repo Url: g...@bitbucket.org:yooture/xxx.git * branch specifier: */master * Repository browser: (auto) * Additional Behaviours: none * Script Path: Jenkinsfile * Lightweight checkout: onIn have the following simele simple pipeline: {code:java}pipeline { agent { label 'lxc-fedora25' } tools { maven 'MVN_352' jdk "Oracle JDK 1.8 (latest)" } stages { stage('build Snapshot') { when { not { branch 'master' } } steps { sh 'mvn clean install -Dmaven.test.failure.ignore' } } stage('Build Release') { when { branch 'master' } steps { sh "mvn clean deploy" } } }}{code} even though the branch specifier is specified as "*/master", "build Snapshot" stage is always executed :(
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50622) when condition not correctly discovering branch
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-50622
when condition not correctly discovering branch
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-04-06 09:31
Environment:
Pipeline Model Definition Plugin: 1.2.2
Priority:
Critical
Reporter:
Dominik Bartholdi
I created a new pipeline job and defined "Pipeline script from SCM" using Git:
repo Url: g...@bitbucket.org:yooture/xxx.git
branch specifier: */master
Repository browser: (auto)
Additional Behaviours: none
Script Path: Jenkinsfile
Lightweight checkout: on
In have the following simele pipeline:
pipeline {
agent { label 'lxc-fedora25' }
tools {
maven 'MVN_352'
jdk "Oracle JDK 1.8 (latest)"
}
stages {
stage('build Snapshot') {
when { not { branch 'master' } }
steps {
sh 'mvn clean install -Dmaven.test.failure.ignore'
}
}
stage('Build Release') {
when { branch 'master' }
steps {
sh "mvn clean deploy"
}
}
}
}
[JIRA] (JENKINS-50622) when condition not correctly discovering branch
Title: Message Title
Dominik Bartholdi commented on JENKINS-50622
Re: when condition not correctly discovering branch
btw. this stage:
stage('prepare yoo') {
steps {
echo "on ${env.BRANCH_NAME}"
}
}
does print 'on null' - I guess this is the root problem, but I have no idea why this is the case...
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50718) append tool HOME to PATH in declarative Pipeline
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-50718
append tool HOME to PATH in declarative Pipeline
Issue Type:
Improvement
Assignee:
Oleg Nenashev
Components:
customtools-plugin
Created:
2018-04-10 14:26
Environment:
custom-tools-plugin: 0.5 Jenkins: 2.89.4.1
Priority:
Minor
Reporter:
Dominik Bartholdi
I have the following custom-tool configured: Name: jx-release-version Install automatically: on Script:
#!/bin/sh
set -e
JX_RELEASE_VERSION=v1.0.10
JX_RELEASE_VERSION_DIR=${HOME}/tools/jx-release-version-${JX_RELEASE_VERSION}
if test ! -x "${JX_RELEASE_VERSION_DIR}"/firefox ; then
mkdir -p "${JX_RELEASE_VERSION_DIR}"
cd "${JX_RELEASE_VERSION_DIR}"
wget https://github.com/jenkins-x/jx-release-version/releases/download/${JX_RELEASE_VERSION}/jx-release-version-linux
mv jx-release-version-linux jx-release-version
chmod 755 jx-release-version
fi
Tool Home: /${HOME}/tools/jx-release-version-v1.0.10 And I try to use it in my pipeline, the tool gets installed, but its HOME is not added to PATH:
pipeline {
agent { label 'lxc-fedora25' }
tools {
'com.cloudbees.jenkins.plugins.customtools.CustomTool' 'jx-release-version'
}
stages {
stage ('step 1') {
steps {
script {
sh "jx-release-version"
}
}
}
[JIRA] (JENKINS-50622) when condition not correctly discovering branch
Title: Message Title Dominik Bartholdi commented on JENKINS-50622 Re: when condition not correctly discovering branch OK, my bad - thanks for the explanation! ...but should this not be aligned somehow? I think it just does not make much sense to have different names in different job types... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50563) support declarative pipeline parameter definition
Title: Message Title Dominik Bartholdi commented on JENKINS-50563 Re: support declarative pipeline parameter definition Hi Marc Rohlfs, I already have a couple of plugins I'm taking care of - so I don't think I can take more than I already have - but if I find time, I might look into this feature request... /Domi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50814) provide a way to keep git credentials
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-50814 provide a way to keep git credentials Issue Type: Improvement Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-04-16 08:19 Priority: Minor Reporter: Dominik Bartholdi This is an enhancement request to support some kind of way to tell the plugin not to delete the git credentials after the checkout. Today when ever I want to pull or push some changes from/to the remote git repository, I have to explicitly set the following configuration in may pipeline: sh "git config --global user.name 'myuser'" sh "git config --global user.email 'myu...@mycomp.com'" # no pull/push works sh "git push ..." This has the major drawback, that now my pipeline script is bound to the credentials configured in my jenkins job. I therefore request a flag/option which I can enable so this information is set (or not removed after the checkout) by the bitbucket multibranch plugin.
[JIRA] (JENKINS-50814) provide a way to keep git credentials
Title: Message Title Dominik Bartholdi assigned an issue to rsandell Jenkins / JENKINS-50814 provide a way to keep git credentials Change By: Dominik Bartholdi Assignee: rsandell Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50815) beside GIT_BRANCH also expose it as BRANCH
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-50815
beside GIT_BRANCH also expose it as BRANCH
Issue Type:
Improvement
Assignee:
Mark Waite
Components:
git-plugin
Created:
2018-04-16 08:39
Priority:
Minor
Reporter:
Dominik Bartholdi
jenkins declarative pipeline has a nice condition to check for branch names:
stage('build Snapshot') {
when { not { branch 'master' } }
steps {
sh 'mvn clean install -Dmaven.test.failure.ignore'
}
}
unfortunate, it only checks for the branch name in `env.BRANCH`. Sure, I can use something like this:
when {
_expression_ { return env.GIT_BRANCH == "master" }
}
but that's not as nice as the former... The other solution for this would be, the pipeline-model-definition-plugin would check for multiple variables (BRANCH_NAME, BRANCH, GIT_BRANCH) and maybe throw an error in case they define different values (except for null). This does not sound like a big issue, but for sure it will make a lot of things easier to understand, e.g. why would the condition behave different in a multibranch job then in a normal job? please also see JENKINS-50622
[JIRA] (JENKINS-50815) beside GIT_BRANCH also expose it as BRANCH
Title: Message Title Dominik Bartholdi commented on JENKINS-50815 Re: beside GIT_BRANCH also expose it as BRANCH Mark Waite the fact that I can not run the pipeline as shown in JENKINS-50622 without multi-branch shows that it does not the way I described it. I would expect to be able to run the same pipeline in a normal pipeline job and in multi-branch, but thats not working. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14109) Passing ${NODE_NAME} as Node Parameter to downstream job not possible on master
Title: Message Title
Dominik Bartholdi commented on JENKINS-14109
Re: Passing ${NODE_NAME} as Node Parameter to downstream job not possible on master
Dhruvit Patel this was fixed way back in 2012 - so any recent version of the nodelabel plugin will have that included, nothing you have to do in particular - just use a recent version. If it does not work for you, please open a new issue and explain the problem in more detail
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41174) Can not save manage script after update
Title: Message Title Dominik Bartholdi edited a comment on JENKINS-41174 Re: Can not save manage script after update I'm not able to reproduce this - I downloaded Jenkins 2.37 and only installed config-file-provider plugin (no other plugins , except the dependencies needed by config-file-provider ) and created some configurations without any issues...Maybe you could add the support information collected by this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41174) Can not save manage script after update
Title: Message Title Dominik Bartholdi commented on JENKINS-41174 Re: Can not save manage script after update I'm not able to reproduce this - I downloaded Jenkins 2.37 and only installed config-file-provider plugin (no other plugins) and created some configurations without any issues... Maybe you could add the support information collected by this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41202) Managed Configuration Files cannot be saved or used
Title: Message Title Dominik Bartholdi commented on JENKINS-41202 Re: Managed Configuration Files cannot be saved or used I would say this is a bug in the openstack-plugin, but I'm quite sure Oliver Gondža already fixed this Caused by: java.lang.IllegalStateException: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! at org.jenkinsci.lib.configprovider.model.Config.getDescriptor(Config.java:108) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40364) Support npm configuration file
Title: Message Title Dominik Bartholdi commented on JENKINS-40364 Re: Support npm configuration file Nikolas Falco do you need an help form my site? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41174) Can not save manage script after update
Title: Message Title Dominik Bartholdi resolved as Fixed a fix will be released today Jenkins / JENKINS-41174 Can not save manage script after update Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40987) Exception when saving the job configuration
Title: Message Title Dominik Bartholdi commented on JENKINS-40987 Re: Exception when saving the job configuration This seems to be caused by the Violations plugin - when saving an instance of this class: https://github.com/jenkinsci/violations-plugin/blob/master/src/main/java/hudson/plugins/violations/TypeConfig.java 2017-01-12 08:47:27.328+ [id=153] WARNING o.e.jetty.util.log.JavaUtilLog#warn: Error while serving http://ourhost.co:8000/job/xxx%20Merge%20Request/configSubmit java.lang.NullPointerException at hudson.plugins.violations.TypeConfig.setUnstable(TypeConfig.java:109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.beanutils.PropertyUtilsBean.invokeMethod(PropertyUtilsBean.java:2170) at org.apache.commons.beanutils.PropertyUtilsBean.setSimpleProperty(PropertyUtilsBean.java:2151) at org.apache.commons.beanutils.PropertyUtils.setSimpleProperty(PropertyUtils.java:890) at org.kohsuke.stapler.RequestImpl.copyProperty(RequestImpl.java:923) at org.kohsuke.stapler.RequestImpl.fill(RequestImpl.java:574) at org.kohsuke.stapler.RequestImpl.bindParameters(RequestImpl.java:391) at hudson.plugins.violations.hudson.ViolationsFreestyleDescriptor.newInstance(ViolationsFreestyleDescriptor.java:66) at hudson.plugins.violations.hudson.ViolationsFreestyleDescriptor.newInstance(ViolationsFreestyleDescriptor.java:22) at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:1050) at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:1012) at hudson.util.DescribableList.rebuildHetero(DescribableList.java:208) at hudson.model.Project.submit(Project.java:236) at hudson.model.Job.doConfigSubmit(Job.java:1245) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:796) why this is the case, I don't know... Add Comment
[JIRA] (JENKINS-40973) Failed to prepare configFileProvider step
Title: Message Title
Dominik Bartholdi commented on JENKINS-40973
Re: Failed to prepare configFileProvider step
there is a typo in your script: field should be fileId
configFileProvider([configFile(fileId: 'my_file', variable: 'capitals_info')])
{
echo "${env.capitals_info}"
echo " == content of json cfg == "
sh "cat ${env.capitals_info}"
}
but this showed my an other issue which I will fix now and then a better message will be displayed to you...
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40973) Failed to prepare configFileProvider step
Title: Message Title
Dominik Bartholdi edited a comment on JENKINS-40973
Re: Failed to prepare configFileProvider step
there is a typo in your script: {{field}} should be {{fileId}} {noformat} configFileProvider([configFile(fileId: 'my_file', variable: 'capitals_info')]){ echo "${env.capitals_info}" echo " == content of json cfg == " sh "cat ${env.capitals_info}" }{noformat}but this showed my an other issue which I will fix now and then a better message will be displayed to you... <
/td>
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40973) Failed to prepare configFileProvider step
Title: Message Title Dominik Bartholdi reopened an issue Jenkins / JENKINS-40973 Failed to prepare configFileProvider step Change By: Dominik Bartholdi Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40973) Failed to prepare configFileProvider step
Title: Message Title Dominik Bartholdi commented on JENKINS-40973 Re: Failed to prepare configFileProvider step Ramanathan M in that case, please provide more information about your environment. Can you reproduce the same issue with a clean/new jenkins installation? and please attache the support information generated by this plugin https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin to this issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40973) Failed to prepare configFileProvider step
Title: Message Title
Dominik Bartholdi edited a comment on JENKINS-40973
Re: Failed to prepare configFileProvider step
[~mramanathan] in that case, please provide more information about your environment. Can you reproduce the same issue with a clean/new jenkins installation? and please attache the support information generated by this plugin https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin to this issue. you should also include the complete {{config.xml}} of the job having this issue
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12114) Flexible file editing permissions
Title: Message Title Dominik Bartholdi resolved as Fixed released with 2.15.5 Jenkins / JENKINS-12114 Flexible file editing permissions Change By: Dominik Bartholdi Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41174) Can not save manage script after update
Title: Message Title Dominik Bartholdi commented on JENKINS-41174 Re: Can not save manage script after update tian tian please upgrade to config-file-provider 2.15.5 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40364) Support npm configuration file
Title: Message Title Dominik Bartholdi commented on JENKINS-40364 Re: Support npm configuration file Nikolas Falco 1. here is an example of a configuration roundtrip: https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test#UnitTest-Configurationroundtriptesting 2. why don't you make the first field a dropdown and use doFillXXXItems - have a look at https://github.com/jenkinsci/config-file-provider-plugin/blob/master/src/main/java/org/jenkinsci/plugins/configfiles/maven/job/MvnSettingsProvider.java#L137-L144 ) This way the user can only select configs from the correct type. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40364) Support npm configuration file
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-40364 Support npm configuration file Change By: Dominik Bartholdi Comment: [~nfalco] 2.15.5 fixes this an was released 2 or 3 days ago Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40364) Support npm configuration file
Title: Message Title Dominik Bartholdi commented on JENKINS-40364 Re: Support npm configuration file Nikolas Falco 2.15.5 fixes this an was released 2 or 3 days ago Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40364) Support npm configuration file
Title: Message Title Dominik Bartholdi commented on JENKINS-40364 Re: Support npm configuration file 1. view.jelly is used when you enable "Provide Configuration files" in "Build environment" and add a new file and click "view selected file":2. yes only show valid configurations in the dropdown - only npmrc config files. ...I don't understand your question: "In this case how does user understand that configuration is wrong instead a bug of plugin?" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40364) Support npm configuration file
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-40364 Support npm configuration file Change By: Dominik Bartholdi Attachment: Screen Shot 2017-01-21 at 20.28.14.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40364) Support npm configuration file
Title: Message Title Dominik Bartholdi commented on JENKINS-40364 Re: Support npm configuration file ok, I think I understand now... 1. I think thats a good idea! (and thanks for the hint about the maven settings being editable!) 2. this also is a very nice idea so both are cool ideas - but if you want to have this, then you have to wait for an upcoming release of the config-file-provider - I'm not sure when I will have time to implement this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41258) Config File Provider Plugin doesn't update files
Title: Message Title Dominik Bartholdi resolved as Fixed please update to the latest version - this was fixed 2.15.5 Jenkins / JENKINS-41258 Config File Provider Plugin doesn't update files Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.go
[JIRA] (JENKINS-41265) Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID
Title: Message Title Dominik Bartholdi assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-41265 Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Cyrille Le Clerc Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41265) Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID
Title: Message Title Dominik Bartholdi commented on JENKINS-41265 Re: Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID I would say this is by design... but I let this to one of the authors of the pipeline-maven plugin: Cyrille Le Clerc Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40973) Failed to prepare configFileProvider step
Title: Message Title Dominik Bartholdi resolved as Not A Defect Jenkins / JENKINS-40973 Failed to prepare configFileProvider step Change By: Dominik Bartholdi Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Dominik Bartholdi commented on JENKINS-41303 Re: Managed Files does not list previous config file after update please add some more information about this issue: what kind of configs are not shown? maven-settings? json? common? ... which other plugins are installed? best would be if you could provide the support information collected by this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Dominik Bartholdi commented on JENKINS-41303 Re: Managed Files does not list previous config file after update I'm really sorry about the issues you guys face!! here I'm now a bit confused though are you (Anil Belur, Thanh Ha and Rick Liu) all talking about the same issue? did you save your configuration before you upgraded any of the plugins? If so, please load this configuration again with config-file-provider 2.13 and then do an upgrade to 2.15.5 this is the most recent version and fixes some very important things (e.g. update of existing configs) do you have an errors in the logs? can you provide the support information collected by this plugin? https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin how does the content of org.jenkinsci.plugins.configfiles.GlobalConfigFiles.xml look like? which types of configuration files did you have configured before the upgrade? (xml? maven? json? ...?) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. F
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Dominik Bartholdi commented on JENKINS-41303 Re: Managed Files does not list previous config file after update all versions < 2.15 use multiple configuration files on global scope (one for each configuration type, maven, json, openstack, ...) all versions > 2.15.x use a single configuration file per scope (1 for global, 1 for each folder - only if you configure any config files on folder scope). As soon as you upgrade to a version > 2.15.x the file per config type are empty and later even removed - so you can not downgrade again, unless you still have the original files. This is the reason why your update center did show you a red warning before you upgraded to this version of the plugin. If you have openstack config files, then you might have had an issue during migration and this comment should help you to fix it: https://github.com/jenkinsci/openstack-cloud-plugin/pull/121#issuecomment-272463391 In any case, you can check if you do have any occurrence of org.jenkinsci.lib.configprovider.model.Config in the org.jenkinsci.plugins.configfiles.GlobalConfigFiles.xml - if so, then you there is a problem and you can either use the same approach described in the reverenced comment above or just remove all these entries from that file. So if you still have the original type specific configuration files, then the easiest is to restore them together with version 2.13 of the config-file-provider and then upgrade to version 2.15.5 (nothing below!). Anil Belur, thanks for the support.zip - unfortunate the most important files are seem to be removed from the zip: there are no log files (did you remove them?) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41767) Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Title: Message Title Dominik Bartholdi commented on JENKINS-41767 Re: Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method I changed the code of the config-file-provider to be more binary compatible with older versions. But please note: rolling back from config-file-provider >= 1.15 to <= 1.13 will not recover any configuration - you will have to restore configuration from your backups. This is because config-file-provider 1.15 changed the format and location where the files are stored. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Dominik Bartholdi commented on JENKINS-41303 Re: Managed Files does not list previous config file after update Denis Syrokvash config-file-provider >= 1.15 changed the internal format used to store the configuration, so this is correct. You should not see org.jenkinsci.lib.configprovider.model.Config anywhere anymore - it is not a valid configuration. If you see this in the file org.jenkinsci.plugins.configfiles.GlobalConfigFiles.xml, then for sure you will also see errors. What different types of config-files do you had configured in config-file-provider before you upgraded to > 1.15.*? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title
Dominik Bartholdi commented on JENKINS-41303
Re: Managed Files does not list previous config file after update
Denis Shvedchenko this will not work anymore you need to use the specific class - org.jenkinsci.lib.configprovider.model.Config is not a valid type (actually, it should be abstract):
def loadConfigForProvider(provider, configs) {
configs.each { spec ->
def config = new org.jenkinsci.plugins.configfiles.custom.CustomConfig(spec.id, spec.name, spec.comment, getContentForSpec(spec))
config.setProviderId(provider.getProviderId());
provider.save(config);
}
}
you could also create an instance of the new config like this:
def config = provider.newConfig(spec.id) {noformat) ...but the problem here is, that the config does not have setters for the single fields
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title
Dominik Bartholdi edited a comment on JENKINS-41303
Re: Managed Files does not list previous config file after update
[~dshvedchenko] this will not work anymoreyou need to use the specific class - {{org.jenkinsci.lib.configprovider.model.Config}} is not a valid type (actually, it should be abstract):{noformat} def loadConfigForProvider(provider, configs) {configs.each { spec -> def config = new org.jenkinsci.plugins.configfiles.custom.CustomConfig(spec.id, spec.name, spec.comment, getContentForSpec(spec)) config.setProviderId(provider.getProviderId()); provider.save(config);} }{noformat}you could also create an instance of the new config like this:{noformat} def config = provider.newConfig(spec.id) {noformat ) } ...but the problem here is, that the {{config}} does not have setters for the single fields
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title
Dominik Bartholdi edited a comment on JENKINS-41303
Re: Managed Files does not list previous config file after update
[~dshvedchenko] this will not work anymoreyou need to use the specific class - {{org.jenkinsci.lib.configprovider.model.Config}} is not a valid type (actually, it should and will be be abstract in the future ):{noformat} def loadConfigForProvider(provider, configs) {configs.each { spec -> def config = new org.jenkinsci.plugins.configfiles.custom.CustomConfig(spec.id, spec.name, spec.comment, getContentForSpec(spec)) config.setProviderId(provider.getProviderId()); provider.save(config);} }{noformat}you could also create an instance of the new config like this:{noformat} def config = provider.newConfig(spec.id) {noformat}...but the problem here is, that the {{config}} does not have setters for the single fields
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title
Dominik Bartholdi edited a comment on JENKINS-41303
Re: Managed Files does not list previous config file after update
[~dshvedchenko] this will not work anymoreyou need to use the specific class - {{org.jenkinsci.lib.configprovider.model.Config}} is not a valid type (actually, it should and will be be abstract in the future):{noformat} def loadConfigForProvider(provider, configs) {configs.each { spec -> def config = new org.jenkinsci.plugins.configfiles.custom.CustomConfig(spec.id, spec.name, spec.comment, getContentForSpec(spec)) config.setProviderId(provider.getProviderId()); provider.save(config);} }{noformat}you could also create an instance of the new config like this:{noformat} def config = provider.newConfig(spec.id) {noformat}...but the problem here is, that the {{config}} does not have setters for the single fields one more note to be more clear: the class {{org.jenkinsci.plugins.configfiles.custom.CustomConfig}} is a different for each provider - each provider only works with its own implementation of a config class - so the above example only works if the provider is an instance of {{org.jenkinsci.plugins.configfiles.custom.CustomConfig.CustomConfigProvider}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Dominik Bartholdi commented on JENKINS-41303 Re: Managed Files does not list previous config file after update Denis Shvedchenko can you please create an other issue with your problem and assign it to me? ...I started to work on a solution for this problem Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Dominik Bartholdi commented on JENKINS-41303 Re: Managed Files does not list previous config file after update sorry, I think I was not clear enough about the new ticket - the issue with the "class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!" will not be solved by this (this is caused by the wrong usage of the NEW api) - but I'm working on a solution to allow you dynamic creation of a config via provider. So the important part for the new ticket would be the script you use. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!
Title: Message Title Dominik Bartholdi started work on JENKINS-41871 Change By: Dominik Bartholdi Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!
Title: Message Title Dominik Bartholdi commented on JENKINS-41871 Re: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! I will provide a solution to create new configs dynamically. Beside this, your last comment is about the best hint I got about an other issue: I did not know that emailext is also using the config-file-provider plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method!
Title: Message Title Dominik Bartholdi commented on JENKINS-41871 Re: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! Denis Shvedchenko could you provide a hudson.plugins.emailext.GroovyTemplateConfig.xml and maybe also hudson.plugins.emailext.JellyTemplateConfig.xml configuration file which was used prior you upgraded to config-file-provider 2.15.*? That would make it a lot simpler for me to test the upgrade Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41303) Managed Files does not list previous config file after update
Title: Message Title Dominik Bartholdi commented on JENKINS-41303 Re: Managed Files does not list previous config file after update every one using the email-ext plugin, please see: JENKINS-41936 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41936) configuration not migrated
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-41936 configuration not migrated Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2017/Feb/10 4:58 PM Priority: Major Reporter: Dominik Bartholdi all installations which used email-ext plugin together with the config-file-provider plugin < 2.15.* loose there configuration because the config-file-provider plugin is not able to migrate the configuration. The commit causing this is: https://github.com/jenkinsci/email-ext-plugin/commit/e266800286856dc98bb1de211026cad383a712aa Add Comment
[JIRA] (JENKINS-41078) Cannot provision via jcloud (google-compute-engine)
Title: Message Title Dominik Bartholdi edited a comment on JENKINS-41078 Re: Cannot provision via jcloud (google-compute-engine) [~felfert] tahts thats a bug in the config-file-provider and was fixed a couple of days a go, I'll update the PR to depend on the latest version Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41078) Cannot provision via jcloud (google-compute-engine)
Title: Message Title Dominik Bartholdi commented on JENKINS-41078 Re: Cannot provision via jcloud (google-compute-engine) Fritz Elfert tahts a bug in the config-file-provider and was fixed a couple of days a go, I'll update the PR to depend on the latest version Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) provide a way to create configs via script
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-41871 provide a way to create configs via script Change By: Dominik Bartholdi Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) provide a way to create configs via script
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-41871 provide a way to create configs via script Change By: Dominik Bartholdi Summary: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! provide a way to create configs via script Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) provide a way to create configs via script
Title: Message Title Dominik Bartholdi commented on JENKINS-41871 Re: provide a way to create configs via script with version 2.15.6 it is now possible to create a new config file like this: provider.newConfig(id, name, comment, content) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41871) provide a way to create configs via script
Title: Message Title Dominik Bartholdi resolved as Fixed Jenkins / JENKINS-41871 provide a way to create configs via script Change By: Dominik Bartholdi Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42226) NPE in branch condition
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-42226
NPE in branch condition
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Feb/21 4:55 PM
Priority:
Minor
Reporter:
Dominik Bartholdi
This pipeline fails with a NullPointerException:
config = [:]
pipeline {
agent any
stages {
stage ('prepare') {
when {
branch config.branch
}
steps {
echo "hello branch"
}
}
}
}
exception:
java.lang.NullPointerException
at org.jenkinsci.plugins.pipeline.modeldefinition.when.impl.BranchConditional.branchMatches(BranchConditional.java:64)
at org.jenkinsci.plugins.pipeline.modeldefinition.when.impl.BranchConditional$branchMatches.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:18)
[JIRA] (JENKINS-42226) NPE in branch condition
Title: Message Title
Dominik Bartholdi updated an issue
Jenkins / JENKINS-42226
NPE in branch condition
Change By:
Dominik Bartholdi
This pipeline fails with a {{NullPointerException}}:{noformat}config = [:]pipeline {agent anystages {stage ('prepare') {when {branch config.branch}steps {echo "hello branch"}}}}{noformat} I know, the pipeline might look a bit strange with having a config/map defined - but in our real pipeline, we have some logic to select the correct config/map object before the pipeline starts. This allows us to reuse a lot more... exception:{noformat}java.lang.NullPointerException at org.jenkinsci.plugins.pipeline.modeldefinition.when.impl.BranchConditional.branchMatches(BranchConditional.java:64) at org.jenkinsci.plugins.pipeline.modeldefinition.when.impl.BranchConditional$branchMatches.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:18){noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42226) NPE in branch condition
Title: Message Title Dominik Bartholdi commented on JENKINS-42226 Re: NPE in branch condition Andrew Bayer that was fast - thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42262) Provide a method where extension could implement own logic for the content of custom Config
Title: Message Title Dominik Bartholdi commented on JENKINS-42262 Re: Provide a method where extension could implement own logic for the content of custom Config thats a good idea - I'll see what I can do (or more when time allows... ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39898) allow exclusion of branches
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-39898 allow exclusion of branches Change By: Dominik Bartholdi Attachment: Screen Shot 2017-02-24 at 16.33.52.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39898) allow exclusion of branches
Title: Message Title Dominik Bartholdi commented on JENKINS-39898 Re: allow exclusion of branches well, there is no advanced section in the "bitbucket team/project" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39898) allow exclusion of branches
Title: Message Title Dominik Bartholdi reopened an issue Jenkins / JENKINS-39898 allow exclusion of branches Change By: Dominik Bartholdi Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39898) allow exclusion of branches
Title: Message Title Dominik Bartholdi edited a comment on JENKINS-39898 Re: allow exclusion of branches [~stephenconnolly] well, there is no advanced section in the "bitbucket team/project" (at least not in the version installed on DEV@cloud by cloudbees) !Screen Shot 2017-02-24 at 16.33.52.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12928) Job name Enforcer
Title: Message Title Dominik Bartholdi commented on JENKINS-12928 Re: Job name Enforcer Sagayaraj David this was introduced way longer then folders even exist - please open a new feature request if you wold like this to be changed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42338) default tools not installed on agent
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-42338
default tools not installed on agent
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Feb/27 10:05 AM
Priority:
Major
Reporter:
Dominik Bartholdi
given the following pipeline, I would expect the java version "1.8" to be printed, but this is not the case - instead I get "1.7"; the default version of the underlying system.
pipeline {
agent none
tools {
jdk "Oracle JDK 1.8 (latest)"
}
stages {
stage ('prepare') {
agent any
steps {
sh "java -version"
}
}
}
}
but this one works as:
pipeline {
agent any
tools {
jdk "Oracle JDK 1.8 (latest)"
}
stages {
stage ('prepare') {
steps {
sh "java -version"
}
}
}
}
...my expectation is, that the tools on top scope are installed on all agents.
[JIRA] (JENKINS-42340) run launches agent even when not required
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-42340
run launches agent even when not required
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Feb/27 10:17 AM
Priority:
Critical
Reporter:
Dominik Bartholdi
given the following pipeline, I would expect the "with NO agent" stage to trigger without any agent being launched. This is not the case, all stages are launched with an agent. This is specially a problem when I have an "input" step waiting for a user interaction in one of the stages defined.
pipeline {
agent any
tools {
jdk "Oracle JDK 1.8 (latest)"
}
stages {
stage ('with any agent 0') {
steps
sh "java -version"
}
}
stage ('with NO agent') {
agent none
steps {
sh "java -version"
}
}
stage ('with any agent 1') {
steps {
sh "java -version"
}
}
}
}
btw. I was only able to discover this because of JENKINS-42338 - I think it would also be a good idea to have the "stage" step print some info on which agent it actually runs.
[JIRA] (JENKINS-42340) stage launches agent even when not required
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-42340 stage launches agent even when not required Change By: Dominik Bartholdi Summary: run stage launches agent even when not required Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42340) stage launches agent even when not required
Title: Message Title
Dominik Bartholdi updated an issue
Jenkins / JENKINS-42340
stage launches agent even when not required
Change By:
Dominik Bartholdi
given the following pipeline, I would expect the "with NO agent" stage to trigger without any agent being launched. This is not the case, all stages are launched with an agent. This is specially a problem when I have an "input" step waiting for a user interaction in one of the stages defined.{noformat}pipeline {agent anytools {jdk "Oracle JDK 1.8 (latest)"}stages {stage ('with any agent 0') {steps sh "java -version"}} stage ('with NO agent') {agent nonesteps {sh "java -version"}}stage ('with any agent 1') {steps {sh "java -version"}}}}{noformat} This is also the case where "with NO agent" is the first stage in the pipeline. btw. I was only able to discover this because of JENKINS-42338 - I think it would also be a good idea to have the "stage" step print some info on which agent it actually runs.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42335) OLE Object creation fails
Title: Message Title Dominik Bartholdi commented on JENKINS-42335 Re: OLE Object creation fails Homolya Peter sorry, but I'm not able to help you with any of this; maybe someone in the community is able to do so... ...I don't have windows and I also don't have excel but as you have a running installation: can't you figure out the difference between your test and live installation? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42335) OLE Object creation fails
Title: Message Title Dominik Bartholdi assigned an issue to Unassigned Jenkins / JENKINS-42335 OLE Object creation fails Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42340) stage launches agent even when not required
Title: Message Title Dominik Bartholdi commented on JENKINS-42340 Re: stage launches agent even when not required and how would you define an input step which can wait for say 2 days? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42340) stage launches agent even when not required
Title: Message Title Dominik Bartholdi edited a comment on JENKINS-42340 Re: stage launches agent even when not required and how would you define an _input_ step which can wait for say 2 days? also I think together with JENKINS-42338 this means I have to duplicate the same configuration over and over again. Because I have to define _agent none_ on top scope and redefeine every agent for each _stage_ again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42433) Allow Scriptler to be used in Post Build
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-42433 Allow Scriptler to be used in Post Build Change By: Dominik Bartholdi Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42389) Modifying Folder configuration removes all config files
Title: Message Title Dominik Bartholdi assigned an issue to Dominik Bartholdi Jenkins / JENKINS-42389 Modifying Folder configuration removes all config files Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-42473
Cannot get property 'stages' on null object
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Mar/03 5:00 PM
Environment:
pipeline model definition: 1.0.1 Jenkins: 2.32.2.4 (DEV@Cloud by cloudbees)
Priority:
Major
Reporter:
Dominik Bartholdi
I have the following simple pipeline:
@Library("yooture@test")
import org.foo.Zot
pipeline {
agent any
stages {
stage('Example') {
steps {
echo 'Hello World'
}
}
}
post {
always {
echo 'I will always say Hello again!'
}
}
}
I have the same pipeline in two separate repos in a branch called `develop` (copy/paste). In the repo called 'dummy' the job runs fine and the output is like this:
Started by user Dominik Bartholdi
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@bitbucket.org:yooture/dummy.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:yooture/dummy.git
> git --version # timeout=10
using GIT_SSH to set credentials empty PK to force use of cloudbees dev PK
> git fetch --tags --progress g...@bitbucket.org:yootur
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title
Dominik Bartholdi commented on JENKINS-42473
Re: Cannot get property 'stages' on null object
to make the whole thing even more strange, I tried the following: I forked a branch from 'yooture/develop' repository (repo/branch) to yooture/feature/empty_branch_test2 and it works:
Branch indexing
Cloning the remote Git repository
Cloning repository g...@bitbucket.org:yooture/yooture.git
> git init /home/yooture/hudson_home/workspace/_feature_empty_branch_test2-TR4FWR4O7Y5ZH2REBHUBTGTVWO2ULVEWLS4DS4YN6RJIJTTJZVWQ@script # timeout=10
Fetching upstream changes from g...@bitbucket.org:yooture/yooture.git
> git --version # timeout=10
using GIT_SSH to set credentials empty PK to force use of cloudbees dev PK
> git fetch --tags --progress g...@bitbucket.org:yooture/yooture.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url g...@bitbucket.org:yooture/yooture.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url g...@bitbucket.org:yooture/yooture.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:yooture/yooture.git
using GIT_SSH to set credentials empty PK to force use of cloudbees dev PK
> git fetch --tags --progress g...@bitbucket.org:yooture/yooture.git +refs/heads/feature/empty_branch_test2
Checking out Revision fb7b7daa3ee2d456edd67b7ec00f944edd969526 (feature/empty_branch_test2)
> git config core.sparsecheckout # timeout=10
> git checkout -f fb7b7daa3ee2d456edd67b7ec00f944edd969526
First time build. Skipping changelog.
[Bitbucket] Notifying commit build result
Loading library yooture@test
> git rev-parse --is-inside-work-tree # timeout=10
Setting origin to g...@bitbucket.org:yooture/yooture-jenkins-pipeline-libraries.git
> git config remote.origin.url g...@bitbucket.org:yooture/yooture-jenkins-pipeline-libraries.git # timeout=10
Fetching origin...
Fetching upstream changes from origin
> git --version # timeout=10
> git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
> git rev-parse test^{commit} # timeout=10
> git rev-parse origin/test^{commit} # timeout=10
Cloning the remote Git repository
Cloning repository g...@bitbucket.org:yooture/yooture-jenkins-pipeline-libraries.git
> git init /home/yooture/hudson_home/workspace/_feature_empty_branch_test2-TR4FWR4O7Y5ZH2REBHUBTGTVWO2ULVEWLS4DS4YN6RJIJTTJZVWQ@libs/yooture # timeout=10
Fetching upstream changes from g...@bitbucket.org:yooture/yooture-jenkins-pipeline-libraries.git
> git --version # timeout=10
> git fetch --tags --progress g...@bitbucket.org:yooture/yooture-jenkins-pipeline-libraries.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url g...@bitbucket.org:yooture/yooture-jenkins-pipeline-libraries.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url g...@bitbucket.org:yooture/yooture-jenkins-pipeline-libraries.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:yooture/yooture-jenkins-pipeline-libraries.git
> git fetch --tags --progress g...@bitbucket.org:yooture/yooture-jenkins-pipeline-libraries.git +refs/heads/*:refs/remotes/origin/*
Checking out Revision 3ca0c91267dcdad0ca87753530d6ccc72052de6d (test)
> git config core.sparsecheckout # timeout=10
> git checkout -f 3ca0c91267dcdad0ca87753530d6ccc72052de6d
First time build. Skipping changelog.
[Bitbucket] Notifying commit build result
[Pipeline] node
R
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title Dominik Bartholdi commented on JENKINS-42473 Re: Cannot get property 'stages' on null object yeah, and only in one specific branch in one repo... - is there any kind of cache that could hold on on something for any reason? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title Dominik Bartholdi commented on JENKINS-42473 Re: Cannot get property 'stages' on null object ah and btw. if I remove/comment the Library and import stuff from the top, then it works... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title Dominik Bartholdi commented on JENKINS-42473 Re: Cannot get property 'stages' on null object I would really love to test it, but you would need to convince your colleagues running DEV@cloud - since they have this new approval process and release cycles its a pain in the a... to get anything updated in a reasonable time... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title Dominik Bartholdi commented on JENKINS-42473 Re: Cannot get property 'stages' on null object its an org folder (bitbucket) - but dev@cloud does not allow the download of config.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-42473 Cannot get property 'stages' on null object Change By: Dominik Bartholdi Comment: its an org folder (bitbucket) - but dev@cloud does not allow the download of config.xml :( Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-42473 Cannot get property 'stages' on null object Change By: Dominik Bartholdi Attachment: config.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title Dominik Bartholdi commented on JENKINS-42473 Re: Cannot get property 'stages' on null object its a bitbucket org folder.. - file attached Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-42473 Cannot get property 'stages' on null object Change By: Dominik Bartholdi Attachment: config-org.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42473) Cannot get property 'stages' on null object
Title: Message Title Dominik Bartholdi edited a comment on JENKINS-42473 Re: Cannot get property 'stages' on null object its a bitbucket org folder.. - file attached , both for failing job and org Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24034) Clarify meaning of "Id" and "Name" fields
Title: Message Title Dominik Bartholdi commented on JENKINS-24034 Re: Clarify meaning of "Id" and "Name" fields Id is not only internal, if you reference a script from within the TokenMacro plugin, then the id must be used: https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin#ScriptlerPlugin-TokenMacroSupport The name is only there for display purposes Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15878) scriptler explicit classpath
Title: Message Title Dominik Bartholdi commented on JENKINS-15878 Re: scriptler explicit classpath I would think in direction of @Grape as its supported by pipeline: https://jenkins.io/doc/book/pipeline/shared-libraries/#using-third-party-libraries Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42621) Using Numerical Comparison for conditional build step via DSL
Title: Message Title Dominik Bartholdi closed an issue as Not A Defect this feature already exists - see screenshot Jenkins / JENKINS-42621 Using Numerical Comparison for conditional build step via DSL Change By: Dominik Bartholdi Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-42621) Using Numerical Comparison for conditional build step via DSL
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-42621 Using Numerical Comparison for conditional build step via DSL Change By: Dominik Bartholdi Attachment: Screen Shot 2017-03-10 at 09.41.50.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42389) Modifying Folder configuration removes all config files
Title: Message Title Dominik Bartholdi commented on JENKINS-42389 Re: Modifying Folder configuration removes all config files Evaristo Gutierrez I also asked on the ML for some hints on how to resolve this issue - unfortunate with no luck ...maybe you could ask around internally? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
