Skip to content

PDP-518: Changing the workspace permissions #1783

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

SameeraPriyathamTadikonda
Copy link
Contributor

So we can incorporate your pull request, please share the following:

  • What issue are you addressing with this pull request?
  • Are you modifying the correct branch? (See CONTRIBUTING.md)
  • Have you run unit tests? (See CONTRIBUTING.md)
  • Version of MarkLogic Java Client API (see Readme.txt)
  • Version of MarkLogic Server (see admin gui on port 8001)
  • Java version (java -version)
  • OS and version
  • What Changed: What happened before this change? What happens without this change?

@Copilot Copilot AI review requested due to automatic review settings July 3, 2025 18:52
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds calls to updateWorkspacePermissions() in multiple pipeline post blocks to ensure workspace permissions are updated before tearing down Docker containers.

  • Inserts updateWorkspacePermissions() before tearDownDocker() in each pipeline stage’s post block.

@@ -180,6 +180,7 @@ pipeline{
}
post {
always {
updateWorkspacePermissions()
Copy link
Preview

Copilot AI Jul 3, 2025

Choose a reason for hiding this comment

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

Repeated calls to updateWorkspacePermissions() across multiple pipeline post blocks introduce duplication. Consider extracting this into a shared function or leveraging a declarative pipeline global post section to DRY up the configuration.

Suggested change
updateWorkspacePermissions()

Copilot uses AI. Check for mistakes.

Copy link
Contributor

Choose a reason for hiding this comment

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

This seems like good advice - tearDownDocker is called in 5 places, and in each place, updateWorkspacePermissions needs to be called as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, I'll be creating another shared library for docker cleanup as well. I've separated these two to use this function for non-docker environments as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We run our stages in parallel on different nodes, global post stage will clean up only on the last node.

@@ -180,6 +180,7 @@ pipeline{
}
post {
always {
updateWorkspacePermissions()
Copy link
Contributor

Choose a reason for hiding this comment

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

This seems like good advice - tearDownDocker is called in 5 places, and in each place, updateWorkspacePermissions needs to be called as well.

@SameeraPriyathamTadikonda SameeraPriyathamTadikonda merged commit 1b329f1 into marklogic:develop Jul 3, 2025
2 checks passed
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.

2 participants