[JIRA] [plain-credentials-plugin] (JENKINS-28528) Secret File deleted before post build Action
Title: Message Title
Simon Devineau created an issue
Jenkins / JENKINS-28528
Secret File deleted before post build Action
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
plain-credentials-plugin, sonar
Created:
21/May/15 3:41 PM
Environment:
Jenkins 1.599 Plain Credentials Plugin 1.1 SonarQube plugin 2.2
Labels:
plugin jenkins slave sonar-plugin
Priority:
Major
Reporter:
Simon Devineau
Hello everyone,
I have a job with a maven goal clean install In advanced option I set up the user settings.xml as follow $ {userSettings.xml}
where this variable is a binding from a secret file I created.
During the maven build, the same file is used but with a different uuid clean install
s D:-
---\secretFiles\e9b970a0-46b8-482e-bc1b-aca37e28ec52\settings-jenkins.xml
[JIRA] [plain-credentials-plugin] (JENKINS-28528) Secret File missing during post build Action
Title: Message Title Simon Devineau updated an issue Jenkins / JENKINS-28528 Secret File missing during post build Action Change By: Simon Devineau Summary: SecretFile deletedbefore missingduring postbuildAction 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] [role-strategy-plugin] (JENKINS-19934) Add Job Create permission to project roles
Simon Devineau commented on JENKINS-19934 Add Job Create permission to project roles Ok thanks for your consideration. I will commit a new version on monday. I had some bugs in my code. 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] [role-strategy-plugin] (JENKINS-19934) Add Job Create permission to project roles
Simon Devineau
commented on JENKINS-19934
Add Job Create permission to project roles
Hello everyone,
First I would like to say thank you to Oleg and his team. This plugin is so powerfull.
About this/these bug(s), I am sorry if I did not understand everything but here is my aim.
I want a user (let's call him jobCreator) to be able to create jobs only if it respects a pattern otherwiswe it does not create it.
If the user has the global create job he can do whatever he wants (Let's call him globalCreator)
As it was said above, you need the global create job to be able to see the icon 'Create new item'.
So the jobCreator will always have both permisisons (global and job)
The globalCreator needs to have ONLY the global create permissions.
I have modified the code of RoleBasedProjectNamingStrategy to follow my scenario.
I cannot promise anything with it but if you want to check it out and update your code with, I will be glad.
Also, I am not sure the current code is working.
//firstly check global role
SortedMapRole, SetString gRole = rbas.getGrantedRoles(RoleBasedAuthorizationStrategy.GLOBAL);
for (SortedMap.EntryRole, SetString entry: gRole.entrySet()){
if (entry.getKey().hasPermission(Item.CREATE))
return;
}
This will always return true because gRole contains all the users with all the global permissions.
It should check the current logged user.
I am gonna patch my code to your github if you are interested and attached it to my message.
Could you please let me know about your intention.
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] [role-strategy-plugin] (JENKINS-19934) Add Job Create permission to project roles
Simon Devineau updated JENKINS-19934 Add Job Create permission to project roles Here is the code I modified to follow my scenario Change By: Simon Devineau (13/Mar/15 4:05 PM) Attachment: RoleBasedProjectNamingStrategy.java 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] [maven-plugin] (JENKINS-27161) RedeployPublisher does not really parse the global settings from Config File Provider Plugin
Simon Devineau created JENKINS-27161 RedeployPublisher does not really parse the global settings from Config File Provider Plugin Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 27/Feb/15 2:22 PM Description: Hello, I try to use the RedeployPublisher but I have trouble to provide server credentials. Return code is: 401, ReasonPhrase: Unauthorized. The RedeployPublisher uses the settings.xml located in the maven installation conf folder. Maven RedeployPublisher use remote com.--.slave maven settings from : D:\apps\jenkins\com.-.slave\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.2.1/conf/settings.xml If I set this file with the server info : server iddeploymentRepo/id usernamerepouser/username passwordrepopwd/password /server it works well. But I cannot really set up this file as it is an automatic install and I have several slaves. Besides I would need to do it for each version of maven. When I set up the server credentials in my global maven from the plugin Config File Provider Plugin and remove the server section in the D:\apps\jenkins\com.--.slave\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.2.1/conf/settings.xml I am not able to publish anymore. I guess the RedeployPublisher does not really parse the global settings from the Config File Provider Plugin. regards Environment: Jenkins 1.599 Config File Provider Plugin 2.7.5 Project: Jenkins Labels: maven plugin redeploy Priority: Major Reporter: Simon Devineau 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] [maven-plugin] (JENKINS-27161) RedeployPublisher does not really parse the global settings from Config File Provider Plugin
Simon Devineau updated JENKINS-27161 RedeployPublisher does not really parse the global settings from Config File Provider Plugin Change By: Simon Devineau (27/Feb/15 2:34 PM) Description: Hello,ItrytousetheRedeployPublisherbutIhavetroubletoprovideservercredentials.Returncodeis:401,ReasonPhrase:Unauthorized.TheRedeployPublisherusesthesettings.xmllocatedinthemaveninstallationconffolder.MavenRedeployPublisheruseremotecom.---.slavemavensettingsfrom:D:\apps\jenkins\com.--.slave\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.2.1/conf/settings.xmlIfIsetthisfilewiththeserverinfo:serveriddeploymentRepo/idusernamerepouser/usernamepasswordrepopwd/password/serveritworkswell.ButIcannotreallysetupthisfileasitisanautomaticinstallandIhaveseveralslaves.BesidesIwouldneedtodoitforeachversionofmaven.WhenIsetuptheservercredentialsinmyglobalmavenfromthepluginConfigFileProviderPluginandremovetheserversectionintheD:\apps\jenkins\com.--.slave\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.2.1/conf/settings.xmlIamnotabletopublishanymore.IguesstheRedeployPublisherdoesnotreallyparsetheglobalsettingsfromtheConfigFileProviderPlugin eventifitiswrittenusingglobalsettingsconfigwithname . .. regards 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] [maven-plugin] (JENKINS-27161) RedeployPublisher does not really parse the global settings from Config File Provider Plugin
Simon Devineau updated JENKINS-27161 RedeployPublisher does not really parse the global settings from Config File Provider Plugin Change By: Simon Devineau (27/Feb/15 3:02 PM) Attachment: jenkins.png 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.
