![]() |
|
|
|
|
Change By:
|
Jo Vandeginste
(06/Mar/15 5:27 PM)
|
|
Description:
|
TL;DR:
I'm trying to use Jenkins credentials in combination with the Git SCM plugin in jobs in subfolders. They work with jobs in folders at the root level, but I can't seem to use them with jobs in folders within folders.
The longer explanation:
I am trying to set up a hiearchy of jobs using the Cloudbees-folders plugin and role strategy based on teams (and their projects).
Abstract example:
teamA/projectA1/
teamA/projectA2/
teamB/projectB1/
Each folder and subfolder can have several jobs.
I'm also using the credentials plugin to manage eg. Git username/password.
For my first tests I put a lot of jobs in the first level (teamA), and used a specific set of credentials in combination with the git SCM plugin to automate the git clone (without hardcoding my credentials in a shell script). Every job used the same set of credentials, for they accessed the same repository server.
This worked like a charm!
Then I started organizing in subfolders (eg. teamA/projectA1) and I found no way to use any set of credentials in the (moved) jobs. Creating new jobs didn't help: same behaviour. Trying with Subversion didn't work either.
The concrete problem I experienced was this:
Normally when creating or updating a job, you may pick an SCM so Jenkins will clone your repository for you as an early step in your job. You can enter Repository URL and pick Credentials (or use the "Add" button to add credentials). Normally the credential picker will preselect "- none -" and will contain the other available credentials (depending on some factors). In case of jobs in subfolders, the picker is completely empty and using the "Add" button does nothing at all. The result
it
is
that the repository can not be
clone
cloned
because it lacks credentials.
Can anyone tell me if I'm just blind and missing some obvious thing, or if there is some known problem that I didn't find on the Internet? I simply can't believe I'm the first one to try and use this combination of functionalities.
Thanks in advance
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
