Skip to content

Conversation

@mbritense
Copy link
Contributor

WIP

mbritense and others added 15 commits January 7, 2026 15:06
…in-dependencies

# Conflicts:
#	backend/building-block/src/main/kotlin/com/ritense/buildingblock/configuration/BuildingBlockAutoConfiguration.kt
…ugin-dependencies

story: building block zaak instance link and zaak type link dependencies warning
# Conflicts:
#	backend/building-block/src/main/kotlin/com/ritense/buildingblock/security/config/BuildingBlockHttpSecurityConfigurer.kt
#	frontend/projects/valtimo/building-block-management/src/lib/components/building-block-management-detail/building-block-management-detail.component.html
#	frontend/projects/valtimo/building-block-management/src/lib/components/building-block-management-detail/building-block-management-detail.component.ts
…locks

feat: building blocks draft functionality
@marijnritense marijnritense temporarily deployed to pr-test-environment January 8, 2026 14:50 — with GitHub Actions Inactive
mbritense and others added 9 commits January 9, 2026 11:34
…tion-module-to-blueprint

feat: rename solution module to blueprint
…g-block-final-case-def-finalize

# Conflicts:
#	frontend/projects/valtimo/shared/src/lib/generated/generated-backend-types.ts
…ing-block-final-case-def-finalize

feat: case definition can only be finalized if all building blocks it uses are final
@ivo-ritense ivo-ritense added the test env Create a remote test environment for this PR in the Ritense product development cluster label Jan 13, 2026
@valtimo-platform
Copy link
Contributor

valtimo-platform bot commented Jan 13, 2026

Will create a test environment. This comment will be updated once it is available. This usually takes a few minutes.
Closing or merging this PR will automatically delete the test environment. Pushing commits to this PR will update the test environment.
Progress:

  • Created test environment
  • Waiting for frontend and backend images with tag "testEnv.pr83\_commit.\<commit sha\>\_contents.\<contents sha\>\_build.\<build number\>". Check the GitHub Actions logs for progress on the build / image tagging.
  • Starting test environment
  • Waiting for environment to run

@sjorsholtrop-ritense
Copy link
Contributor

@mbritense When this PR built its frontend image, it didn't tag it properly for the test env since that tagging step didn't exist yet. But if you make any change to the frontend, it will build + tag the image properly, and the test env will work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test env Create a remote test environment for this PR in the Ritense product development cluster

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants