Request for hosting a new plugin: APICoverage
Hello there! This is a request to host a plugin called API Coverage. The details are: Url: https://github.com/rackerlabs/api-coverage Repo name: api-coverage-plugin Personal GitHub: pritic Jenkins Account: pritichanglani Description: The API Coverage plugin will serve as a tool to measure testing of the API contract Thank you, Priti -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d2b29e8b-be73-4fec-8e4a-5deb218d73c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: 1.609.3 RC posted
It does not seems to be published. [1] gives 404 and [2] serves 1.609.1-rc (not even 1.609.2-rc). [1] http://mirrors.jenkins-ci.org/war-stable-rc/1.609.3/jenkins.war [2] http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/baed07fe-1a7d-4394-b30c-d40b222b737c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Office Hour for August 12: Workflow plugin
Thanks for the session. I was really informative and useful :) On Tuesday, 11 August 2015 19:26:37 UTC+5:30, Jesse Glick wrote: On Tue, Aug 11, 2015 at 7:32 AM, Vinodhini Vijay vinodhi...@gmail.com javascript: wrote: The event time is showing 11:00am PDT in https://wiki.jenkins-ci.org/display/JENKINS/Office+Hours , but pointing to a different time. I tried to change, but it is not reflecting the new time. It was mistakenly pointing to last week; fixed. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/383e8cdb-a0da-40ce-a694-c2c2f2b4eddb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Why did my Jira issues vanish?
Hi Daniel, hi Christopher, many thanks for the information and for having a look! FYI: I just checked some local records and I am almost sure that I created the tickets on July 22nd. Kind regards Marc On Wednesday, August 12, 2015 at 11:06:23 PM UTC+2, Daniel Beck wrote: On 12.08.2015, at 12:28, Christopher Orr ch...@orr.me.uk javascript: wrote: http://jenkins-ci.org/content/wiki-and-issue-tracker-outage-over-weekend http://osuosl.org/blog/mysql1-vip-post-mortem -- though most data could be restored, some data from between the 15th and the 17th was lost. Ouch. Looks like I was a bit too optimistic in the blog post. I'll try to find the affected issues and notify the creators. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f197ed35-5ceb-41eb-aacb-8ee1d77dcc97%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Why did my Jira issues vanish?
Hi, I just tested by manually changing the urls: It looks like issues from JENKINS-29432 up to JENKINS-29468 are missing. JENKINS-29431 created 15/Jul/15 12:09 PM is still accessible JENKINS-29469 created 17/Jul/15 5:43 AM is accessible again. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1bc46b27-373a-481d-aa7f-7752b848d238%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Why did my Jira issues vanish?
OK, seems like my local records where misleading. My ticket *must* have been created in the period You mentioned. Bad luck :( I think I'll recreate the issues some time the next days, but with just a very basic description ... On Thursday, August 13, 2015 at 4:09:52 PM UTC+2, Björn Pedersen wrote: Hi, I just tested by manually changing the urls: It looks like issues from JENKINS-29432 up to JENKINS-29468 are missing. JENKINS-29431 created 15/Jul/15 12:09 PM is still accessible JENKINS-29469 created 17/Jul/15 5:43 AM is accessible again. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f08ce1b0-ada0-4f6e-af0a-6bbb413fde1b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for hosting a plugin for QF-Test integration
Hello Daniel, I've added the wiki page as described. Could you guide me how to make it available again? Should I republish the wiki page or can you fix the DB issue ? Best regards, Thomas Original Message On 12.08.2015, at 18:54, Christopher Orr ch...@orr.me.uk wrote: This is happening because your wiki page (mysteriously) does not exist: https://wiki.jenkins-ci.org/display/JENKINS/QF-Test+Plugin It looks like it's there, but if you add something to the end of the URL to bypass the cache, you can see that it's missing (possibly deleted, but I think that shows a different message if so): https://wiki.jenkins-ci.org/display/JENKINS/QF-Test+Plugin?foo Since a wiki page is required, and you currently don't have one, that's why your plugin isn't appearing in the Update Centre. Could this be a victim of the DB issue? Judging from the earlier email's date, the wiki page may well have been created between 15th and 17th of July. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/55CCA8DF.7060109%40qfs.de. For more options, visit https://groups.google.com/d/optout.
Re: Why did my Jira issues vanish?
I've come to the same conclusion in https://jenkins-ci.org/content/update-wiki-and-issue-tracker-outage I'm currently writing an email to all affected users, asking them to re-post everything that's still relevant. Thanks to the jenkinsci-issues list, we know most of what was lost. On 13.08.2015, at 16:09, Björn Pedersen icee...@googlemail.com wrote: Hi, I just tested by manually changing the urls: It looks like issues from JENKINS-29432 up to JENKINS-29468 are missing. JENKINS-29431 created 15/Jul/15 12:09 PM is still accessible JENKINS-29469 created 17/Jul/15 5:43 AM is accessible again. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/B34B6600-85D4-4A48-95BF-A8B4195406C9%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
Re: Data loss in the Jenkins CI issue tracker
CC'ed to the dev list. Recipients in BCC. On 13.08.2015, at 17:04, Daniel Beck m...@beckweb.net wrote: Hi, The Jenkins project recently experienced a data loss in the issue tracker. Read more about it here: https://jenkins-ci.org/content/update-wiki-and-issue-tracker-outage I'm writing to you because I've determined that you took some action in Jira during the approximately 37 hours we lost, based on the notification emails sent to the jenkinsci-issues mailing list (which archives notifications from JIRA): http://groups.google.com/group/jenkinsci-issues/topics Please take a moment to go to that Google group, and look for messages containing your jenkins-ci.org user name or email address that were posted between July 15 and July 17. You can search for your email address on the Google Group above to find notifications involving you. If you find that you posted reports or comments in the mailing list between July 15 and July 17 that are missing on the actual issue tracker but would still be relevant, please consider posting them again in JIRA. You can get the full text of what you wrote from the jenkinsci-issues mailing list. Thank you for your help! Daniel -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/16E4BFB6-C7FC-4551-AD74-D8E96A253C0D%40beckweb.net. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/84C2E4F2-EB93-48FA-85E2-5BBFA7199D00%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
Re: Request: contributor rights for maven-metadata-plugin
FYI: I was added now. Many thanks! On Tuesday, August 11, 2015 at 12:49:31 PM UTC+2, poma...@googlemail.com wrote: Hi there, I created some pull request for the maven-metadata-plugin https://github.com/jenkinsci/maven-metadata-plugin repository. The owner of the plugin now informed me that he can hardly maintain it anymore. He suggest that I ask for contributor rights and merge and release to PRs myself. Please see his comment on one of the pull requests https://github.com/jenkinsci/maven-metadata-plugin/pull/7#issuecomment-127273922 . Can anybody provide me with contributor rights for that plugin? What do I need to do to get them? BTW: My GitHub account is marcrohlfs https://github.com/marcrohlfs. Many thanks in advance! Kind regards Marc -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1c73620e-bd9b-4bd1-8902-b25dfa82a0f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: commit access powershell plugin
Only a month ago, Chris Albrecht (in CC) asked for the same thing (and should have been granted access). https://groups.google.com/d/msgid/jenkinsci-dev/a969eeb3-d3fe-426d-a0bd-2ea1017f154e%40googlegroups.com Could you please coordinate your efforts? On 04.08.2015, at 20:34, Alexander Heubusch alexander.heubu...@gmail.com wrote: Hello Everyone, Requestiong commit acces for the powershell plugin https://github.com/jenkinsci/powershell-plugin GitHub: aheubusch jenkins-ci.org: aheubusch Last publish 2009, last commit 2014. I can also take on the role of maintainer. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/dd1cb450-e88d-4610-bebe-53dc6c770e6e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2A77DA9F-4BCF-4EC5-8D65-CC8A341AE34F%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
Re: Hosting for New Plugin: jboss-deploy
Hi Daniel, Sorry about the delay! I made you a committer of the jboss-plugin. Please note that in general, we try to retain backwards compatibility with users' data if at all possible. Otherwise, plugin major versions are generally increased to indicate an incompatible change, and the new version declared incompatible with the old one. https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions You could also make use of the experimental update center before releasing any new version to existing users to solicit feedback. http://jenkins-ci.org/content/experimental-plugins-update-center Daniel On 30.07.2015, at 20:29, Daniel Bustamante Ospina dbustamant...@gmail.com wrote: Hi Daniel, Performing the merge can be a good idea, but the jboss-plugin is a bit outdated and it is based on a rather old version of jboss, nonetheless I could try to do it, but, could you give me commit access on this repository? 2015-07-30 10:06 GMT-05:00 Daniel Beck m...@beckweb.net: Hi Daniel, would it make sense to merge this and e.g. the jboss-plugin to provide comprehensive functionality in one place? On 27.07.2015, at 23:21, Daniel Bustamante Ospina dbustamant...@gmail.com wrote: Hi everyone, I've created a plugin for jboss deployment that I'd like to share with the Jenkins community. Repo: https://github.com/Daniel69/deploy-jboss-plugin Plugin name: deploy-jboss GitHub username: Daniel69 Jenkins username: dbustamante69 There are a couple of plugins that one could believe that are similar to this (deploy-plugin and jboss-plugin), but there is a big difference in the approach, this plugin is specially built for lastests mayor versions of JBoss and JBoss EAP (using jboss-as-controller-client) and supports deployments in domain mode as well as in standalone mode , which can not be achieved with the approach of neither mentioned plugins. ~Daniel. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ef3c0354-21e6-4a0e-befa-8195ee12fa91%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Developers group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/AxwuXVuRLyo/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CB6AED5F-5A7C-4CD9-81F6-E30CC16AD89C%40beckweb.net. For more options, visit https://groups.google.com/d/optout. -- -- Daniel Bustamante Ospina -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJNALEZK%3DQc2PAORz6_iVigMbiM-n1%2BfojQFcWVWsaP1saHbMA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/49D46E4A-0350-450A-8E40-0BDAB14CE64E%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
Data loss in the Jenkins CI issue tracker
Hi, The Jenkins project recently experienced a data loss in the issue tracker. Read more about it here: https://jenkins-ci.org/content/update-wiki-and-issue-tracker-outage I'm writing to you because I've determined that you took some action in Jira during the approximately 37 hours we lost, based on the notification emails sent to the jenkinsci-issues mailing list (which archives notifications from JIRA): http://groups.google.com/group/jenkinsci-issues/topics Please take a moment to go to that Google group, and look for messages containing your jenkins-ci.org user name or email address that were posted between July 15 and July 17. You can search for your email address on the Google Group above to find notifications involving you. If you find that you posted reports or comments in the mailing list between July 15 and July 17 that are missing on the actual issue tracker but would still be relevant, please consider posting them again in JIRA. You can get the full text of what you wrote from the jenkinsci-issues mailing list. Thank you for your help! Daniel -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/16E4BFB6-C7FC-4551-AD74-D8E96A253C0D%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
Re: Request for hosting: Publish to Dropbox plugin
Hi René, I forked your plugin to https://github.com/jenkinsci/publish-over-dropbox-plugin and made you a committer. Tell us your jenkins-ci.org (wiki, issue tracker) user name and we'll create JIRA component for your plugin with you as lead. Note that the wiki page you reference in the pom.xml does not exist, and the update center will not publish plugins with invalid wiki URLs. Daniel On 12.04.2015, at 21:42, René De Groot rcgr...@gmail.com wrote: Hello, I would like to request hosting for a plugin I created. It concerns a plugin extending the existing Publish-over base-plugin with Dropbox functionality. This allows you to send artifacts to your Dropbox account without running a synchronizing client on your build server. This will save you bandwidth and will make adding slaves easier. I have the project available at Github: https://github.com/rcgroot/jenkins-publish-over-dropbox-plugin My plugin name: Publish Over Dropbox My personal GitHub ID: rcgroot The existing GitHub repository to fork: https://github.com/rcgroot/jenkins-publish-over-dropbox-plugin.git Licence: MIT Binary: https://github.com/rcgroot/jenkins-publish-over-dropbox-plugin/releases/tag/1.0-rc1 The project is based heavily influenced by the publish-over-ftp project as that was where I learned most of the Jenkins plugin development from. Regards, René -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/24d2f92d-990e-4ecb-98cc-4883927ff23a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2EA5632C-CA87-4630-9D96-13AE7DF4DFDD%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
Re: Request for hosting a plugin for QF-Test integration
On 13.08.2015, at 16:25, Thomas Max thomas@qfs.de wrote: I've added the wiki page as described. Could you guide me how to make it available again? Should I republish the wiki page or can you fix the DB issue ? It's like the page never existed, the data has been lost. See: https://jenkins-ci.org/content/update-wiki-and-issue-tracker-outage I recreated it with a very short description to make the plugin available during the next update center generator run. It's probably best if you just add the content to it again. I archived the cached text before I recreated it, contact me directly and I'll send it to you. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C2E94C70-6DFF-4860-9F73-E5121166CC02%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
Re: Data loss in the Jenkins CI issue tracker
On Thu, Aug 13, 2015 at 11:04 AM, Daniel Beck m...@beckweb.net wrote: look for messages containing your jenkins-ci.org user name or email address that were posted between July 15 and July 17 Tip: https://groups.google.com/forum/#!searchin/jenkinsci-issues/YOURNAMEHERE%7Csort:date -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr06wCCD0zCgRZ4A6gFVGfjHUEMYeh2ACNmf4X9XaB3_ng%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: docker-commons support for DOCKER_CONFIG
On Wed, Aug 12, 2015 at 6:39 PM, nicolas de loof nicolas.del...@gmail.com wrote: Let's say I have slave with 2 executors, and two jobs running docker push to registry, with distinct credentials, running concurrently - job 1 do set .docker/config.json with credentials c1 - job 2 do set .docker/config.json with credentials c2 - job 1 do run docker push, expecting c1 well set for registry - push fails, as c2 does not allow to push to this repository AFAIK this is not an issue in the current plugin because the registry URL is a key in the JSON. Unless you mean that they are both trying to access the _same_ registry, and this registry has some accounts which are read-only and some which allow push. Theoretically possible though it seems unlikely. Anyway if we can use the 1.8 feature then of course we should do it. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1yoW5K%2BhKMgTsZL0ig3V0hhrRQ_DTTXnbDsjMuXDeBwQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
scm-sync-configuration-plugin: unable to run unit tests
Hi, I checked out the master branch of scm-sync-configuration-plugin. When I run the tests of this project I get errors starting from HudsonExtensionsGitTest. Is this only on my computer? Can someone else run these tests successfully? My configuration: Windows7, IntelliJ IDEA 14, JDK 1.6.0_45, git 1.9.5.msysgit.1. Some output: Running hudson.plugins.scm_sync_configuration.repository.HudsonExtensionsGitTest 13-aug-2015 22:13:28 hudson.plugins.scm_sync_configuration.SCMManipulator scmConfigurationSettledUp INFO: Creating scmRepository connection data .. 13-aug-2015 22:13:28 hudson.plugins.scm_sync_configuration.scms.SCM getConfiguredRepository INFO: Creating SCM repository object for url : scm:git:C:\Users\bottemav\AppData\Local\Temp\SCMSyncConfigTestsRoot10033751663327083315368144785423\localRepo 13-aug-2015 22:13:28 hudson.plugins.scm_sync_configuration.scms.SCM getConfiguredRepository INFO: Populating host data into SCM repository object ... 13-aug-2015 22:13:28 hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness initializeRepository INFO: Initializing SCM repository for scm-sync-configuration plugin ... 13-aug-2015 22:13:28 hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness initializeRepository INFO: Directory [C:\Users\bottemav\AppData\Local\Temp\SCMSyncConfigTestsRoot10033751663327083315368144785423\hudsonRootDir\scm-sync-configuration\checkoutConfiguration] created ! [INFO] Executing: cmd.exe /X /C git clone C\Users\bottemav\AppData\Local\Temp\SCMSyncConfigTestsRoot10033751663327083315368144785423\localRepo C:\Users\bottemav\AppData\Local\Temp\SCMSyncConfigTestsRoot10033751663327083315368144785423\hudsonRootDir\scm-sync-configuration\checkoutConfiguration [INFO] Working directory: C:\Users\bottemav\AppData\Local\Temp\SCMSyncConfigTestsRoot10033751663327083315368144785423\hudsonRootDir\scm-sync-configuration 13-aug-2015 22:13:28 hudson.plugins.scm_sync_configuration.SCMManipulator checkout SEVERE: [checkout] Error during checkout : The git-clone command failed. || fatal: repository 'C\Users\bottemav\AppData\Local\Temp\SCMSyncConfigTestsRoot10033751663327083315368144785423\localRepo' does not exist [INFO] Executing: cmd.exe /X /C git add -- config.xml [INFO] Working directory: C:\Users\bottemav\AppData\Local\Temp\SCMSyncConfigTestsRoot10033751663327083315368144785423\hudsonRootDir\scm-sync-configuration\checkoutConfiguration 13-aug-2015 22:13:28 hudson.plugins.scm_sync_configuration.SCMManipulator addFile SEVERE: Error while adding SCM file : fatal: Not a git repository (or any of the parent directories): .git -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bd9ed6d3-ccdf-4d9b-b1ce-3e60753ec6c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: docker-commons support for DOCKER_CONFIG
2015-08-13 20:46 GMT+02:00 Jesse Glick jgl...@cloudbees.com: On Wed, Aug 12, 2015 at 6:39 PM, nicolas de loof nicolas.del...@gmail.com wrote: Let's say I have slave with 2 executors, and two jobs running docker push to registry, with distinct credentials, running concurrently - job 1 do set .docker/config.json with credentials c1 - job 2 do set .docker/config.json with credentials c2 - job 1 do run docker push, expecting c1 well set for registry - push fails, as c2 does not allow to push to this repository AFAIK this is not an issue in the current plugin because the registry URL is a key in the JSON. Unless you mean that they are both trying to access the _same_ registry, and this registry has some accounts which are read-only and some which allow push. Yes exactly, typically accessing dockerhub to push to project repositories, each team having distinct credentials Theoretically possible though it seems unlikely. Anyway if we can use the 1.8 feature then of course we should do it. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1yoW5K%2BhKMgTsZL0ig3V0hhrRQ_DTTXnbDsjMuXDeBwQ%40mail.gmail.com . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzn7X5cavOd_UvMopKxU8kmos0H%2BT8nUMhK6yEsTiHPEWA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
