[JIRA] (JENKINS-49135) Support for reusable sharing Declarative directives
Title: Message Title Daniel Geißler commented on JENKINS-49135 Re: Support for reusable sharing Declarative directives The linked PR is closed since Nov 2018. Have there been any other ideas or actions on this ticket? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187971.1516801165000.418.1573726321230%40Atlassian.JIRA.
[JIRA] (JENKINS-43775) java.util.ConcurrentModificationException when calling junit() step in parallel pipeline branch
Title: Message Title Daniel Geißler commented on JENKINS-43775 Re: java.util.ConcurrentModificationException when calling junit() step in parallel pipeline branch Same here today in a parallel block test execution (declarative pipeline): Jenkins: 2.176.3 JUnit Plugin : 1.27 java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909) at java.util.ArrayList$Itr.next(ArrayList.java:859) at hudson.tasks.junit.TestResult.getResultByNodes(TestResult.java:656) at hudson.tasks.junit.TestResult.getResultByNode(TestResult.java:647) at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:57) at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:23) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Strange thing is that we've never had this in structural pipelines so far, although they run in parallel too. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-53362) Update documentation for junit pipeline step return value
Title: Message Title Daniel Geißler created an issue Jenkins / JENKINS-53362 Update documentation for junit pipeline step return value Issue Type: Improvement Assignee: Unassigned Components: junit-plugin Created: 2018-08-31 09:02 Priority: Minor Reporter: Daniel Geißler I just recently saw a discussion on gitter, where Jesse Glick mentioned that the junit task returns a hudson.tasks.junit.TestResultSummary. This is a very cool feature and I bet many people like to use it, but I couldn't find it anywhere in the official documentation. Jesse Glick @jglick Aug. 30 23:00 @sshepel you need to use the return value from the junit step, as above Serhii Shepel @sshepel Aug. 30 23:01 But ATM currentBuild.rawBuild.getAction(AbstractTestResultAction.class) returns summary for all mvn test calls... hm I didn't know that junit has return value interesting so, does this means that smth like this should work: def platformTestResults = junit allowEmptyResults: true, testResults: '*/target/surefire-reports/.xml'? Jesse Glick @jglick Aug. 30 23:33 @sshepel yes Serhii Shepel @sshepel 00:08 Ok, thanks @jglick will check that tomorrow Serhii Shepel @sshepel 00:33 @jglick hm, decided to do a quick test, and got failure... What kind of value junit step shout return? I thought that it should be hudson.tasks.junit.TestResultAction, am I wrong? oh, strange it returns hudson.tasks.junit.TestResultSummary then how can I get failureDiffString Jesse Glick @jglick 02:16 .failCount as previously mentioned Serhii Shepel
[JIRA] (JENKINS-40997) Add way to get locked resource name in pipeline
Title: Message Title Daniel Geißler commented on JENKINS-40997 Re: Add way to get locked resource name in pipeline Just to link the workaround from Anton Lundin as long as it is not implemented: https://issues.jenkins-ci.org/browse/JENKINS-34268?focusedCommentId=281694=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-281694 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-38510) Add a count to the locks to allow limited ressources
Title: Message Title Daniel Geißler commented on JENKINS-38510 Re: Add a count to the locks to allow limited ressources Well i've read this request in a scenario where some people use the lockable resources plugin to manage RAM (a obviously limited resource) used by their builds. They define x MBytes of RAM as resource (imagine definining 2gb ram in 10mb blocks...), label them and one build locks resources of that label. The definition of a resource with a quantity and the ability to reserve n parts of it, would be super helpful in this case and as far as i see it's not manageable with the Throttle Concurrent Builds 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-38510) Add a count to the locks to allow limited ressources
Title: Message Title Daniel Geißler updated an issue Jenkins / JENKINS-38510 Add a count to the locks to allow limited ressources Change By: Daniel Geißler Comment: Well i've read this request in a scenario where some people use the lockable resources plugin to manage RAM (a obviously limited resource) used by their builds.They define x MBytes of RAM as resource (imagine definining 2gb ram in 10mb blocks...), label them and one build locks resources of that label. The definition of a resource with a quantity and the ability to reserve n parts of it, would be super helpful in this case and as far as i see it's not manageable with the Throttle Concurrent Builds 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-41535) NodeJS installation configuration is not persisted to file
Title: Message Title Daniel Geißler edited a comment on JENKINS-41535 Re: NodeJS installation configuration is not persisted to file Same Issues here (with Jenkins 2.32.1 LTS) and i can confirm that the global tool configuration is lost when jenkins is restarted. 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-41535) NodeJS installation configuration is not persisted to file
Title: Message Title Daniel Geißler commented on JENKINS-41535 Re: NodeJS installation configuration is not persisted to file Same Issues here and i can confirm that the global tool configuration is lost when jenkins is restarted. 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-38510) Add a count to the locks to allow limited ressources
Title: Message Title Daniel Geißler commented on JENKINS-38510 Re: Add a count to the locks to allow limited ressources Why not defining 3 resources with 1 label and assigning the job to lock 1 resources out of that label pool? That way you ll have a max of 3 concurrent job-executions that are using the same label. This may be a bit cumbersome if you'd like to keep the locks job specific, but it s at least possible. 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-39865) Multibranch: Git credentials are not used on checkout scm
Title: Message Title Daniel Geißler closed an issue as Not A Defect Sorry, it was just a old Jenkinsfile with wrong credential Id and not using the "checkout scm" step. Jenkins / JENKINS-39865 Multibranch: Git credentials are not used on checkout scm Change By: Daniel Geißler Status: Open Closed 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
[JIRA] (JENKINS-39865) Multibranch: Git credentials are not used on checkout scm
Title: Message Title Daniel Geißler created an issue Jenkins / JENKINS-39865 Multibranch: Git credentials are not used on checkout scm Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Nov/18 12:53 PM Environment: Jenkins 2.19.3 Pipeline: Multibranch 2.9.2 Priority: Major Reporter: Daniel Geißler I've configured global credentials for SSH username and private key. They are used by a multibranch pipeline project to access a git repository. Indexing is working fine and the branch job is created. Started > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to ...Playground.git > git config remote.origin.url ...Playground.git # timeout=10 Fetching & pruning origin... Fetching upstream changes from origin > git --version # timeout=10 using GIT_SSH to set credentials Jenkins Private Key for Git Access > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune ... But the Branch Job itself is unable to access the repository: Branch indexing > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to ..Playground.git > git config remote.origin.url ..Playground.git # timeout=10 Fetching origin... Fetching upstream changes from origin > git config --get remote.origin.url # timeout=10 using GIT_SSH to
[JIRA] (JENKINS-39829) Ubuntu Installation Instructions lead to "Protocol "http" not supported or disabled in libcurl"
Title: Message Title Daniel Geißler updated an issue Jenkins / JENKINS-39829 Ubuntu Installation Instructions lead to "Protocol "http" not supported or disabled in libcurl" Change By: Daniel Geißler Environment: lsb_release -aNo LSB modules are available. Distributor ID: UbuntuDescription:Ubuntu 16.04.1 LTSRelease:16.04Codename: xenial 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-39829) Ubuntu Installation Instructions lead to "Protocol "http" not supported or disabled in libcurl"
Title: Message Title Daniel Geißler updated an issue Jenkins / JENKINS-39829 Ubuntu Installation Instructions lead to "Protocol "http" not supported or disabled in libcurl" Change By: Daniel Geißler Environment: lsb_release -aNo LSB modules are available.Distributor ID: UbuntuDescription:Ubuntu 16.04.1 LTSRelease:16.04Codename: xenial 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-39829) Ubuntu Installation Instructions lead to "Protocol "http" not supported or disabled in libcurl"
Title: Message Title Daniel Geißler created an issue Jenkins / JENKINS-39829 Ubuntu Installation Instructions lead to "Protocol "http" not supported or disabled in libcurl" Issue Type: Bug Assignee: Unassigned Components: other Created: 2016/Nov/17 3:37 PM Labels: jenkins debian ubuntu install documentation Priority: Major Reporter: Daniel Geißler Coming from the main page for Jenkins (jenkins.io), selecting ubuntu/debian installation of the LTS version takes you to https://pkg.jenkins.io/debian-stable/ The installation instructions suggest to add deb https://pkg.jenkins.io/debian-stable binary/ to /etc/apt/sources.list, but if you try to install jenkins with that you'll get: sudo apt-get install jenkins Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: daemon The following NEW packages will be installed: daemon jenkins 0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded. Need to get 68.9 MB/69.0 MB of archives. After this operation, 70.1 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Err:1 https://pkg.jenkins.io/debian-stable binary/ jenkins 2.19.3 Protocol "http" not supported or disabled in libcurl E: Failed to fetch https://pkg.jenkins.io/debian-stable/binary/jenkins_2.19.3_all.deb Protocol "http" not supported or disabled in libcurl E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Changing
[JIRA] [multijob-plugin] (JENKINS-31579) phaseJobs() are being skipped when there are no changes.
Title: Message Title Daniel Geißler commented on JENKINS-31579 Re: phaseJobs() are being skipped when there are no changes. Seems to be fixed by https://github.com/jenkinsci/tikal-multijob-plugin/commit/9ca4518726d7fdb52042f6a2fb8fee4a5a0809c6 Only the release notes for 1.20 (and 119) are missing. 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] [git-plugin] (JENKINS-9016) Git creates usernames based on 'name' not the email.
Title: Message Title Daniel Geißler updated an issue Jenkins / JENKINS-9016 Git creates usernames based on 'name' not the email. Change By: Daniel Geißler Labels: git plugin scm user-experience 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] [release-plugin] (JENKINS-30381) Release Button is not shown in Views
Title: Message Title Daniel Geißler created an issue Jenkins / JENKINS-30381 Release Button is not shown in Views Issue Type: Bug Assignee: Peter Hayes Attachments: release-button-missing.png Components: release-plugin Created: 10/Sep/15 8:21 AM Environment: Jenkins ver. 1.609.2 (LTS) on Linux with Java 1.8 Release-Plugin Version 2.5.3 Labels: plugin gui regression Priority: Minor Reporter: Daniel Geißler Version 2.5.3 introduced the RELEASE Permission. Without that permission noone could see the release buttons anymore, not in the projects view, nor in the views (wich had the release-button-column added). After i added the Release permission to me i see the button in the projects view
[JIRA] [git-plugin] (JENKINS-9016) Git creates usernames based on 'name' not the email.
Title: Message Title Daniel Geißler commented on JENKINS-9016 Re: Git creates usernames based on 'name' not the email. Problem still persists. In my company users are uniquely identified by their email adress not their user.name, so extracting the user name from the email does not work either. Any plans when to fix that? 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] [release-plugin] (JENKINS-27722) upgrade to the release plugin has left the plugin broken
Title: Message Title Daniel Geiler commented on JENKINS-27722 Re: upgrade to the release plugin has left the plugin broken If that's the point then calling the url directly should not work. And a little mentioning in the release notes would be nice. 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] [git-client-plugin] (JENKINS-26417) Allow to customize refspec/tags of the clone/fetch commands
Title: Message Title
Daniel Geiler edited a comment on JENKINS-26417
Re: Allow to customize refspec/tags of the clone/fetch commands
Asfarasicanseetherefspecisnotusedontheinitialclone.Hereistherelevantextractfromabuildwithacleanedworkspace:{noformat}CloningtheremoteGitrepositoryCloningrepositorygitserver:/data/git/MyProject.git/usr/bin/gitinit/data/jenkins/workspace/myjob.checkoutrefspec#timeout=10Fetchingupstreamchangesfromgitserver:/data/git/MyProject.git/usr/bin/git--version#timeout=10usingGIT_SSHtosetcredentialsJenkinsprivatekey/usr/bin/gitfetch--tags--progressgitserver:/data/git/MyProject.git+refs/heads/*:refs/remotes/origin/*/usr/bin/gitconfigremote.origin.urlgitserver:/data/git/MyProject.git#timeout=10/usr/bin/gitconfig--addremote.origin.fetch+refs/heads/*:refs/remotes/origin/*#timeout=10/usr/bin/gitconfigremote.origin.urlgitserver:/data/git/MyProject.git#timeout=10{noformat}thisisdirectlyfollowedby{noformat}Fetchingupstreamchangesfromgitserver:/data/git/MyProject.gitusingGIT_SSHtosetcredentialsJenkinsprivatekey/usr/bin/gitfetch--tags--progressgitserver:/data/git/MyProject.git+refs/heads/development:refs/remotes/origin/development/usr/bin/gitrev-parseorigin/development^{commit}#timeout=10CheckingoutRevisionc5280c05a01a61f2ae43e46a1ee398be27cdc14e(origin/development)/usr/bin/gitconfigcore.sparsecheckout#timeout=10/usr/bin/gitcheckout-fc5280c05a01a61f2ae43e46a1ee398be27cdc14eFirsttimebuild.Skippingchangelog.{noformat}wichisthesameforlaterBuilds.Itestedwith:*JenkinsLatestandgreatest(1.614)*JenkinsOlderbutstable(1.596.3)*git-client1.17.1*git-client1.16.1 *Gitplugin2.3.5 Anyonecanconfirmthis?Wehavesomeoldandheavybranches(withsomebinaries)thatwedonotwanttogetfetchedatanytime.Asoftodaythisisonlypossiblewithsparsecheckouts,buttheyhavethedrawbackthatwecannotpushtagsbacktoremoteafterthebuild.
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] [git-client-plugin] (JENKINS-26417) Allow to customize refspec/tags of the clone/fetch commands
Title: Message Title
Daniel Geiler edited a comment on JENKINS-26417
Re: Allow to customize refspec/tags of the clone/fetch commands
Asfarasicanseetherefspecisnotusedontheinitialclone.Hereistherelevantextractfromabuildwithacleanedworkspace:{noformat}CloningtheremoteGitrepositoryCloningrepositorygitserver:/data/git/MyProject.git/usr/bin/gitinit/data/jenkins/workspace/myjob.checkoutrefspec#timeout=10Fetchingupstreamchangesfromgitserver:/data/git/MyProject.git/usr/bin/git--version#timeout=10usingGIT_SSHtosetcredentialsJenkinsprivatekey/usr/bin/gitfetch--tags--progressgitserver:/data/git/MyProject.git+refs/heads/*:refs/remotes/origin/*/usr/bin/gitconfigremote.origin.urlgitserver:/data/git/MyProject.git#timeout=10/usr/bin/gitconfig--addremote.origin.fetch+refs/heads/*:refs/remotes/origin/*#timeout=10/usr/bin/gitconfigremote.origin.urlgitserver:/data/git/MyProject.git#timeout=10{noformat}thisisdirectlyfollowedby{noformat}Fetchingupstreamchangesfromgitserver:/data/git/MyProject.gitusingGIT_SSHtosetcredentialsJenkinsprivatekey/usr/bin/gitfetch--tags--progressgitserver:/data/git/MyProject.git+refs/heads/development:refs/remotes/origin/development/usr/bin/gitrev-parseorigin/development^{commit}#timeout=10CheckingoutRevisionc5280c05a01a61f2ae43e46a1ee398be27cdc14e(origin/development)/usr/bin/gitconfigcore.sparsecheckout#timeout=10/usr/bin/gitcheckout-fc5280c05a01a61f2ae43e46a1ee398be27cdc14eFirsttimebuild.Skippingchangelog.{noformat}wichisthesameforlaterBuilds.Itestedwith:*JenkinsLatestandgreatest(1.614)*JenkinsOlderbutstable(1.596.3)*git-client1.17.1*git-client1.16.1*Gitplugin2.3.5 and2.3.4 Anyonecanconfirmthis?Wehavesomeoldandheavybranches(withsomebinaries)thatwedonotwanttogetfetchedatanytime.Asoftodaythisisonlypossiblewithsparsecheckouts,buttheyhavethedrawbackthatwecannotpushtagsbacktoremoteafterthebuild. Hopethisistherightplace,orshouldthatbereportedtothegitplugin?
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
[JIRA] [git-plugin] (JENKINS-28516) refsec is not applied on clone (initial fetch)
Title: Message Title Daniel Geiler created an issue Jenkins / JENKINS-28516 refsec is not applied on clone (initial fetch) Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 21/May/15 9:37 AM Environment: Jenkins Latest and greatest (1.614) / Older but stable (1.596.3) git-client 1.17.1 / 1.16.1 git-plugin 2.3.5 / 2.3.4 Labels: git Priority: Major Reporter: Daniel Geiler As far as i can see the refspec is not used on the initial clone. Here is the relevant extract from a build with a cleaned workspace: Cloning the remote Git repository Cloning repository gitserver:/data/git/MyProject.git /usr/bin/git init /data/jenkins/workspace/myjob.checkoutrefspec # timeout=10 Fetching upstream changes from gitserver:/data/git/MyProject.git /usr/bin/git --version # timeout=10 using GIT_SSH to set credentials Jenkins private key /usr/bin/git fetch --tags --progress
[JIRA] [git-client-plugin] (JENKINS-26417) Allow to customize refspec/tags of the clone/fetch commands
Title: Message Title
Daniel Geiler reopened an issue
As far as i can see the refspec is not used on the initial clone.
Here is the relevant extract from a build with a cleaned workspace:
Cloning the remote Git repository
Cloning repository gitserver:/data/git/MyProject.git
/usr/bin/git init /data/jenkins/workspace/myjob.checkoutrefspec # timeout=10
Fetching upstream changes from gitserver:/data/git/MyProject.git
/usr/bin/git --version # timeout=10
using GIT_SSH to set credentials Jenkins private key
/usr/bin/git fetch --tags --progress gitserver:/data/git/MyProject.git +refs/heads/*:refs/remotes/origin/*
/usr/bin/git config remote.origin.url gitserver:/data/git/MyProject.git # timeout=10
/usr/bin/git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
/usr/bin/git config remote.origin.url gitserver:/data/git/MyProject.git # timeout=10
this is directly followed by
Fetching upstream changes from gitserver:/data/git/MyProject.git
using GIT_SSH to set credentials Jenkins private key
/usr/bin/git fetch --tags --progress gitserver:/data/git/MyProject.git +refs/heads/development:refs/remotes/origin/development
/usr/bin/git rev-parse origin/development^{commit} # timeout=10
Checking out Revision c5280c05a01a61f2ae43e46a1ee398be27cdc14e (origin/development)
/usr/bin/git config core.sparsecheckout # timeout=10
/usr/bin/git checkout -f c5280c05a01a61f2ae43e46a1ee398be27cdc14e
First time build. Skipping changelog.
wich is the same for later Builds.
I tested with:
Jenkins Latest and greatest (1.614)
Jenkins Older but stable (1.596.3)
git-client 1.17.1
git-client 1.16.1
Anyone can confirm this?
We have some old and heavy branches (with some binaries) that we do not want to get fetched at any time. As of today this is only possible with sparse checkouts, but they have the drawback that we can not push tags back to remote after the build.
Jenkins / JENKINS-26417
Allow to customize refspec/tags of the clone/fetch commands
[JIRA] [extensible-choice-parameter] (JENKINS-24116) Add external Script options to use in dynamic parameters
Daniel Geißler created JENKINS-24116 Add external Script options to use in dynamic parameters Issue Type: New Feature Assignee: Unassigned Components: extensible-choice-parameter Created: 05/Aug/14 2:39 PM Description: The Groovy System Script allows us to use groovy scripts to populate the parameter selection. The problem is having a number of jobs that use the same script need to maintain it on every job. A externalized configuration like the Global Choice Parameter offers would help a lot. Reusing scriptler plugin may be another idea. Project: Jenkins Priority: Major Reporter: Daniel Geißler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-2374) Master-Slave Workspace Directory Structure Different
Daniel Geißler commented on JENKINS-2374 Master-Slave Workspace Directory Structure Different I had some trouble with the directory structure too, as there are jobs that copy their build results to another jobs workspace. This is done to be able to reuse the results for deployment even if another build is currently running. I know there may be other and better solutions but one is not always able to change all legacy scripts at once, so that caused a lot of unnessesary problems. I think the slave should mirror the master behavior as much as possible and so use the structure configured in the jenkins global configuration that sogabe pointed to. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
