Skip to content

Conversation

@Eddykasp
Copy link
Member

Remove instruction to remove website stage from Jenkinsfile.

It turns out Jenkins always uses the Jenkinsfile from the master branch, so removing the call on the release branch doesn't even have any effect.

This PR serves as a discussion starting point for how we would like to handle this in the future.

Remove instruction to remove website stage from Jenkinsfile

Signed-off-by: Max Kasperowski <[email protected]>
@Eddykasp Eddykasp requested a review from soerendomroes March 13, 2025 14:42
Signed-off-by: Max Kasperowski <[email protected]>
@Eddykasp Eddykasp added this to the Release 0.10.1 milestone May 12, 2025
Copy link
Contributor

@soerendomroes soerendomroes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is the remove Website stuff no longer necessary?

@Eddykasp
Copy link
Member Author

Why is the remove Website stuff no longer necessary?

Because it doesn't do anything and probably never did. The Jenkins build uses the Jenkinsfile defined on the master branch for builds on any branch. So modifying the file only on the branch doesn't actually prevent the website from being built.

@soerendomroes
Copy link
Contributor

Maybe we jsut need a variable to build the website.

@Eddykasp Eddykasp merged commit 75a5dde into master Jul 1, 2025
6 checks passed
@Eddykasp Eddykasp deleted the mka/build-guide-website branch July 1, 2025 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants