There's got to be something missing here, how can I edit the config? all repos in the entire org all get the same unchangeable settings forever? What if I need to add a post-build step or something, can't be completely stranded like that? (Not to mention "View Configuration" is a super-cryptic and confusing way to say "read-only, can't edit because...")

ivanb

You can at least do some things like post-build steps in the jenkinsfile, and when the repository creates the project it will do so with respect to the jenkinsfile. Here is an example to setup discarding builds and scm polling:

properties([
	[$class: 'BuildDiscarderProperty',strategy: [$class: 'LogRotator', numToKeepStr: '10']],
	pipelineTriggers([[$class: "SCMTrigger", scmpoll_spec: "H/5 * * * *"]])
])

Again this is as designed. Everything you need to do can (AFAIK) be done in your Jenkinsfile; a users’ list question.

"View Configuration" is a super-cryptic and confusing way to say "read-only, can't edit because..."

Probably so; a core UX issue.

jglick

Configuration that cannot be reached by the Jenkinsfile is the problem. There are three levels of items in the hierarchy:

1. The organization that scans github for new repositories and creates multi-branch pipeline projects for each
2. The multi-branch pipeline projects that scan each repository for new branches and pull requests and create builds from the Jenkinsfile
3. The builds that are created from the Jenkinsfile.

I'll grant you that the Jenkinsfile will configure everything necessary for the individual builds. However, there seems to be no way to touch the configuration of the multi-branch pipeline jobs created under an organization. Again, if there is some weird other way to reach these settings, I'd be pretty happy, but as it stands, there is a significant amount of configuration left unreachable.

This problem also affect BlueOcean projects. Creating a pipeline via BlueOcean doesn't allow me to set some of the values I need via the UI so I did it through the Jenkinsfile. Not a big deal but still if the point of BlueOcean is to have a visual means to create pipelines this is an oversight that prevents the modification of the triggers portion of the Jenkinsfile. I also had another issue opened up because there's no way in BlueOcean to create a post section in the pipeline unless you go through the Jenkinsfile.

How to use GitLab integration with Jenkins declarative pipeline? I cannot find working documentation about this.

Another use case I'm facing is the ability of configuring project-specific access. I have a situation where a user does not belong to our organization but he still works for us in a specific project. Given the current configuration, I can either give that user no access at all to all of my organization's builds or he can see all of them. I would love to change this specifically in the project he's working. The final configuration would be something like this:

• At the organization level, anyone belonging to my organization can see all the builds.
• If a person does not belong to my organization, then I would link to give that person access to the builds of the project he is working on. Not all the organization's.

Is there any way to do this currently?

mdesanti no. This would require some kind of github-oauth integration.

bmichaud45 repo folder configuration is effectively available in particular cases, but not in general.

All of these discussions are off topic for this issue, which was about the Save and Apply buttons.

jglick
How do I trigger (or configure) a nightly build (build every midnight) via blue ocean?

A user list question.