Skip to content

test: build itk instruction proto straight from repository and remove local copy#992

Open
JakubWorek wants to merge 2 commits into
mainfrom
jakubworek/adjust-itk-pipeline-scripts
Open

test: build itk instruction proto straight from repository and remove local copy#992
JakubWorek wants to merge 2 commits into
mainfrom
jakubworek/adjust-itk-pipeline-scripts

Conversation

@JakubWorek

Copy link
Copy Markdown

Description

Adjusts itk pipeline to use instruction proto straight from cloned itk repository during startup of itk test

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

# the external `a2a-itk` repo and are fetched at test time by
# `itk/run_itk.sh`. It is exercised by the dedicated `itk.yaml` and
# `itk-nightly.yaml` workflows instead.
run: mvn -B package --file pom.xml -fae -pl '!itk' ${{ matrix.os == 'windows-latest' && '-DskipDockerTests=true' || '' }}

@kabir kabir Jul 23, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@JakubWorek I wonder if instead of having to specify -pl !itk in all the GH Actions workflow files, if it might be better to change the parent pom so that the itk module is included in the list of modules, and have a 'itk' profile to enable it?

That will save adjusting all the jobs. We also have other repositories consuming this module, which in some cases need to build a SNAPSHOT of a2a-java, so this will have knock-on effects

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I agree with @kabir: Why not create a itk profile disabled by default in the parent pom that would add the itk module ? So you just enable it in the ITK workflow

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