After tagging the release-7 with rc2 I wanted to start the release job, but I am unable to see "build with parameters" there.
Usually after tagging the release candidate, I do the following :
1) I go to this website and login.
2) Clicked on the "Release-new" menu
3) Then clicked on the "build with parameters"
However this time I do not see any option "build with parameters".
What's you github handle?
I fixed it.
Let me know if you still face the same issue.
I am still facing problem. still can't see "build with parameters".
I am removing "private" setting, there is nothing private there.
could we get a screenshot of what it look like on your side ? Do you get more item from the menu than what you get on another job, or is everything the same ?
Can you please also provide the screenshot of what you can see for release-new job. That would be helpful to identify the issue.
Created attachment 1619976 [details]
screenshot of the new-release job
As requested, i have attached the screen shot of the new release page
ok, so 1) "jenkins, WTF". 2), what happen if you hit build ? I am trying to narrow if the problem is "display issue in the menu", or some permission problem.
I do get the same result when I am not connected, but it ask me to login when I hit "build".
It is a permission problem. Have attached the screenshot for reference
Created attachment 1621330 [details]
Permission issue screenshot during build
The image to show that i'm getting a permission denied error when I try to build
Can you please tell us the parameters for building if it's blocking you. We can trigger on your behalf.
We are currently figuring out the global security configs for the jenkins instance and it may take some time.
I have been currently blocked on building 5.10 as well.
The parameters are:
GERRIT_REFSPEC : v5.10
I have been currently blocked on building 7.0 :
The parameters are :
GERRIT_REFSPEC : v7.0
I have been currently blocked on building 6.6.
The parameters are:
GERRIT_REFSPEC : v6.6
Can you please trigger the build.
So I did the 6.6
https://build.gluster.org/job/release/215/console seems to have failed :/
ok triggering the proper job is better: https://build.gluster.org/job/release-new/104/
We need to trigger a build for 5.11
GERRIT_REFSPEC : v5.11
We need to trigger a build for 7.1
GERRIT_REFSPEC : v7.1
We need to trigger a build for 6.7
GERRIT_REFSPEC : v6.7
I will watch and restart, in case the builders are not working
(In reply to M. Scherer from comment #23)
> I will watch and restart, in case the builders are not working
So, I gave another try at making the job work, can someone in the release engineer group on github try to see if the job is accessible ?
I tried it and I'm facing problems with triggering the job.
This time instead of just an access denied, its giving the below output.
HTTP ERROR 403 Problem accessing //job/release-new/build. Reason: No valid crumb was included in the request
We need to trigger a build for 7.2
GERRIT_REFSPEC : v7.2
Ok so thanks to Deepshika and I being in the same room at the same time, we were able to fiddle with jenkins configuration and this issue should now be solved (seems "build with parameters" requires "build" + "configure", because parameters are likely some form of configuration...).
Can you tell me if the button appear for you ?
I also added hari who was not in the right group for access to release engineering jobs.
Can you confirm this work fine now ?
So this didn't work, but if we add a individual user, this work. So the group name is likely wrong, we will investigate. in the mean time, the access should be ok now.
We need to trigger a build for 7.3
GERRIT_REFSPEC : v7.3
isn't it now in self service ?
Michael, Rinku wasn't able to trigger because he was not logged in and also he was trying to build with dropdown button on jenkins instance.
Closing it now as Rinku and Hari now have enough permission to start the release job.