Closed Max-Serra closed 8 years ago
Anyway, plz try it out with the latest code.
I believe this issue persists from the date this plugin pushed to github
.
It has nothing to do with the version of jenkins
Thx for raising it out. ^_^
Very good Ace,
By the latest code the plan I mentioned above is now working. I'll try out with much more complex one.
Many thanks.
Hi Ace,
I guess we can consider solved this issue. I executed the Coordinator job over a complex setup and it's working fine at the Security perspective and jobs triggering once a user is logged on.
Good to know :muscle:
Hi,
I've enabled the security by the Configure Global Security page, setting up LDAP option and Project-based Matrix Authorization Strategy.
Some details:
Jenkins version 1.631 Coordinator plugin versions: 1.1.1 and 1.2.0-SNAPSHOT (pulled from develop branch)
Scenario 1 with Failure:
Started by user Massimiliano Serra [EnvInject] - Loading node environment variables. Building on master in workspace /jenkins/jobs/coordinator_active_choice_reactive_parameter_2/workspace Atomic Job: active_choice_reactive_parameter_2 not found Build step 'Coordinator' marked build as failure Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: FAILURE
Scenario 2 with success:
Started by user anonymous [EnvInject] - Loading node environment variables. Building on master in workspace /jenkins/jobs/coordinator_active_choice_reactive_parameter_2/workspace Atomic Job ( active_choice_reactive_parameter_2 ) Triggered Atomic Job: active_choice_reactive_parameter_2 # 2 Completed, Result: SUCCESS Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: SUCCESS
Scenario 3 with success:
Scenario 4 failed again: