[JIRA] (JENKINS-52985) Job DSL multibranchPipelineJob branchSources does not have `svn`
Title: Message Title
James Femia updated an issue
Jenkins / JENKINS-52985
Job DSL multibranchPipelineJob branchSources does not have `svn`
Change By:
James Femia
When attempting to use a Scripted Pipeline to execute some Job DSL to create a Multibranch Pipeline, I am unable to specify my branch sources in SVN. The [documentation|https://jenkinsci.github.io/job-dsl-plugin/#path/multibranchPipelineJob-branchSources] and [source code|https://github.com/jenkinsci/job-dsl-plugin/blob/a10a66e3dcc4294deb5177acb7afa50f0b178c81/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/BranchSourcesContext.groovy] indicate that this is simply not implemented. I would expect the following to work:{noformat}node {jobDsl failOnMissingPlugin: true, ignoreExisting: true, sandbox: true, scriptText: '''multibranchPipelineJob("test-generated") {branchSources {svn { location remoteBase ("http://svn/svn/test_repo/trunk") credentials credentialsId ("svn")}}}}'''} {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-52985) Job DSL multibranchPipelineJob branchSources does not have `svn`
Title: Message Title James Femia commented on JENKINS-52985 Re: Job DSL multibranchPipelineJob branchSources does not have `svn` note: Submitted PR https://github.com/jenkinsci/job-dsl-plugin/pull/1139 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52985) Job DSL multibranchPipelineJob branchSources does not have `svn`
Title: Message Title
James Femia created an issue
Jenkins / JENKINS-52985
Job DSL multibranchPipelineJob branchSources does not have `svn`
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2018-08-10 13:48
Environment:
Jenkins LTS 2.121.2 Docker container Job DSL Plugin 1.70
Priority:
Minor
Reporter:
James Femia
When attempting to use a Scripted Pipeline to execute some Job DSL to create a Multibranch Pipeline, I am unable to specify my branch sources in SVN. The documentation and source code indicate that this is simply not implemented. I would expect the following to work:
node {
jobDsl failOnMissingPlugin: true,
ignoreExisting: true,
sandbox: true,
scriptText: '''multibranchPipelineJob("test-generated") {
branchSources {
svn {
location("http://svn/svn/test_repo/trunk")
credentials("svn")
}
}
}
}'''
}
[JIRA] (JENKINS-40352) Duplicate changesets in pipeline jobs
Title: Message Title James Femia commented on JENKINS-40352 Re: Duplicate changesets in pipeline jobs I have a similar issue with SVN changelogs when the repo is checked out on multiple nodes in a pipeline. The same revision items are present in the list, once per checkout. 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-41626) Branch indexing on subversion repo does not work properly
Title: Message Title James Femia updated an issue Jenkins / JENKINS-41626 Branch indexing on subversion repo does not work properly Change By: James Femia Component/s: subversion-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-41626) Branch indexing on subversion repo does not work properly
Title: Message Title James Femia created an issue Jenkins / JENKINS-41626 Branch indexing on subversion repo does not work properly Issue Type: Bug Assignee: Stephen Connolly Components: branch-api-plugin, workflow-multibranch-plugin Created: 2017/Feb/01 2:56 PM Environment: Jenkins 2.32.1, branch-api-plugin 1.11.1, pipeline multibranch 2.9.2, subversion plugin 2.7.1 Priority: Blocker Reporter: James Femia The multibranch indexer does not traverse sub-folders in subversion branches, if their revision is older than the parent directory. Include Branches: tags/*/projects/productname Given this folder structure in the trunk: projects/-> r1 productname/ -> r2 Jenkinsfile -> r3 Branching projects into tags/1.0/projects yields tags/ -> r4 1.0/-> r4 projects/ -> r1 productname/ -> r2 Jenkinsfile -> r3
[JIRA] (JENKINS-41626) Branch indexing on subversion repo does not work properly
Title: Message Title
James Femia updated an issue
Jenkins / JENKINS-41626
Branch indexing on subversion repo does not work properly
Change By:
James Femia
The multibranch indexer does not traverse sub-folders in subversion branches, if their revision is older than the parent directory.{noformat}Include Branches: tags/*/projects/productname{noformat}Given this folder structure in the trunk:{noformat}projects/-> r1 productname/ -> r2Jenkinsfile -> r3{noformat}Branching *projects* into *tags/1.0/projects* yields{noformat}tags/ -> r4 1.0/-> r4projects/ -> r1 productname/ -> r2 Jenkinsfile -> r3{noformat}Note that _r4_ is only applied to the new folders, and the branched folders retain their original revision (because they haven't changed).The expected behaviour here (and surely, the purpose of the multi- branch system), is for it to automatically detect the new branch and generate jobs from its Jenkinsfiles.The branch indexer should be able to work out that the *1.0/* folder didn't exist before, and index everything inside it at least once regardless of its revision.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39174) Help text for projectName does not describe all permitted values
Title: Message Title
James Femia edited a comment on JENKINS-39174
Re: Help text for projectName does not describe all permitted values
It is also important to note that if the Multibranch Pipeline is searching in branch folders with forward slashes in the sub-job names (or any other url-encodable char), it generates sub-jobs with encoded names. Copying the artifacts from these projects require you to specify the folder path, followed by the *url-encoded* name of the job. This is logical in terms of being able to resolve Folders containing jobs in Jenkins, but may trip you up when writing groovy.e.g. if I have a Multibranch project called "MyBranches", with base of {{https://my.repo}}, and I tell it to search for branches in {{/branches/jamie/*}} and it finds {{/branches/jamie/a}} and {{/branches/jamie/b}}, copying artifacts from these jobs requires me to use {{/MyBranches/branches%2Fjamie%2Fa}}.As a side node on that, unless I am using {{java.net.URLEncoder}} wrong, I have to replace the output of encode {{+}} with {{%20}} in order for the string to match the job name if it has spaces in the url path .{noformat}def job_name = '/MyBranches/' + java.net.URLEncoder.encode('branches/jamie/ a spaces in path ', 'UTF-8').replace('+', '%20'){noformat}I also did not know that the *Pipeline Syntax* link from different pages affected the behaviour of the snippet generator.
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
[JIRA] (JENKINS-39174) Help text for projectName does not describe all permitted values
Title: Message Title
James Femia commented on JENKINS-39174
Re: Help text for projectName does not describe all permitted values
It is also important to note that if the Multibranch Pipeline is searching in branch folders with forward slashes in the sub-job names (or any other url-encodable char), it generates sub-jobs with encoded names. Copying the artifacts from these projects require you to specify the folder path, followed by the url-encoded name of the job. This is logical in terms of being able to resolve Folders containing jobs in Jenkins, but may trip you up when writing groovy. e.g. if I have a Multibranch project called "MyBranches", with base of https://my.repo, and I tell it to search for branches in /branches/jamie/* and it finds /branches/jamie/a and /branches/jamie/b, copying artifacts from these jobs requires me to use /MyBranches/branches%2Fjamie%2Fa. As a side node on that, unless I am using java.net.URLEncoder wrong, I have to replace the output of encode + with %20 in order for the string to match the job name.
def job_name = '/MyBranches/' + java.net.URLEncoder.encode('branches/jamie/a', 'UTF-8').replace('+', '%20')
I also did not know that the Pipeline Syntax link from different pages affected the behaviour of the snippet generator.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You
[JIRA] (JENKINS-40182) Branch indexing does not poll its generated subitems
Title: Message Title James Femia commented on JENKINS-40182 Re: Branch indexing does not poll its generated subitems If I understand correctly you mean add the polling instruction into the Jenkinsfile using properties? Will look into it more tomorrow, but after a brief look, I'm struggling with the syntax for this - the snippet generator for properties / Poll SCM generates me this line (verbatim) properties([pipelineTriggers([])]) Is there an example somewhere of what the polling snippet is supposed to look like? 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-40182) Branch indexing does not poll its generated subitems
Title: Message Title
James Femia updated an issue
Jenkins / JENKINS-40182
Branch indexing does not poll its generated subitems
Change By:
James Femia
The attached Jenkinsfile performs an additional checkout step from "some other" location than the Jenkinsfile repo. When used in a multibranch pipeline, changes to the "other" repo are not detected by the branch indexer. A normal pipeline job using the same Jenkinsfile will correctly poll for changes to this other repo.*Test Repo Structure*{noformat}- root-folder |- branches |- branch-a |- foo.txt |- Jenkinsfile |- branch-b |- bar.txt |- Jenkinsfile (same as branch-a) |- other-lib |- baz.txt{noformat}*Pipeline Job* (correct polling) - Poll SCM: Enabled {{(H/10 * * * *)}} - Pipeline script from SCM: {{https://url/to/branches/branch-a}} - Local Module Directory: {{empty}}1. Build once, observe checkout from {{branch-a}} and {{other-lib}} as per Jenkinsfile2. Modify {{other-lib/baz.txt}} in SCM3. Observe polling log detect changes to {{other-lib}}:{noformat}Received SCM poll call on master for PipelinePollTest on 02-Dec-2016 08:17:01https://192.168.0.31/svn/base/branches/personal/jamie/jenkins-bug-repro/branches/branch-a is at revision 43,233Received SCM poll call on master for PipelinePollTest on 02-Dec-2016 08:17:01https://192.168.0.31/svn/base/branches/personal/jamie/jenkins-bug-repro/other-lib is at revision 43,235 (changed from 43,234)Done. Took 47 msChanges found{noformat}*Multibranch Pipeline Job* (branch indexing) - Project Base: {{https://url/to/branches}} - Include Branches: {{*}} - Periodically if not otherwise run: {{1 minute}}1. Initial branch indexing detects both branches and generates subjobs / schedules them2. Modify {{other-lib/baz.txt}} in SCM3. Observe indexing log * does not detect this change * {noformat}Started by timerOpening conection to https://192.168.0.31/svn/base/branches/personal/jamie/jenkins-bug-repro/branches/Checking directory /branches/personal/jamie/jenkins-bug-repro/branches@HEADChecking candidate branch /branches/personal/jamie/jenkins-bug-repro/branches/branch-a@43233Met criteriaNo changes detected in branch-a (still at 43233)Checking candidate branch /branches/personal/jamie/jenkins-bug-repro/branches/branch-b@43233Met criteriaNo changes detected in branch-b (still at 43233)Finished: SUCCESS{noformat}*Expected Result*For the behaviour to be consistent between these two job types - the branch indexer should be able to detect these changes considering comment on JENKINS-34737 stating this polling behaviour is subsumed into the indexing. (https://issues.jenkins-ci.org/browse/JENKINS-34737?focusedCommentId=262423=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-262423)
[JIRA] (JENKINS-40182) Branch indexing does not poll its generated subitems
Title: Message Title James Femia created an issue Jenkins / JENKINS-40182 Branch indexing does not poll its generated subitems Issue Type: Bug Assignee: Unassigned Attachments: Jenkinsfile Components: workflow-multibranch-plugin Created: 2016/Dec/02 8:52 AM Environment: Jenkins 2.19.3 LTS, pipeline multibranch plugin 2.9.2 Labels: pipeline multibranch Priority: Major Reporter: James Femia The attached Jenkinsfile performs an additional checkout step from "some other" location than the Jenkinsfile repo. When used in a multibranch pipeline, changes to the "other" repo are not detected by the branch indexer. A normal pipeline job using the same Jenkinsfile will correctly poll for changes to this other repo. Test Repo Structure - root-folder |- branches |- branch-a |- foo.txt |- Jenkinsfile |- branch-b |- bar.txt |- Jenkinsfile (same as branch-a) |- other-lib |- baz.txt Pipeline Job (correct polling)
[JIRA] (JENKINS-39920) Pipeline job type has no ability to specify the node labels it can run on
Title: Message Title
James Femia commented on JENKINS-39920
Re: Pipeline job type has no ability to specify the node labels it can run on
In a pipeline job you specify which node to run on by putting a `node('label') {}` block in the pipeline script. You don't specify it on the job itself because the the stuff outside node blocks happens on a flyweight executor on the master, while the rest of the job has the ability to run on multiple nodes, dynamically, based on what you write in the script and which bits are in node blocks.
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-39174) Help text for projectName does not describe all permitted values
Title: Message Title James Femia created an issue Jenkins / JENKINS-39174 Help text for projectName does not describe all permitted values Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 2016/Oct/21 2:01 PM Environment: Jenkins 2.19.1 LTS / Copy Artifact Plugin 1.38.1 Labels: documentation pipeline Priority: Minor Reporter: James Femia According to jglick in #jenkins, the projectName parameter for Copy Artifact can accept absolute and relative paths to jobs in folders. There is no mention of this anywhere in the user-facing documentation. Add Comment
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title James Femia commented on JENKINS-38268 Re: Parallel step and closure scope Same issue here in 2.19.1 LTS / Pipeline 2.4 Thought cloning the closure might be a workaround but it had no effect. Now trying to work around it with more copy and paste of code that would have been in the closure, instead. 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] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title James Femia commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" We are having the same issue, already running slave.jar as a scheduled task on login so the suggested workaround does not help us Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title James Femia edited a comment on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" We are having the same issue with slaves running on Win10 in VMWare , already running slave.jar as a scheduled task on login so the suggested workaround does not help us Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-31527) multijob plugin throws NPE
Title: Message Title James Femia commented on JENKINS-31527 Re: multijob plugin throws NPE I also encounter this issue in 1.20 and 1.18 when using the "Build only if SCM changes" option on a phase job, if the job referenced by that phase job is already in progress. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
