Skip to content

Include RIC pr target in GitHub action #193

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

Merged
merged 2 commits into from
Dec 4, 2020
Merged

Include RIC pr target in GitHub action #193

merged 2 commits into from
Dec 4, 2020

Conversation

stefanbotez
Copy link
Contributor

Description of changes:

  • Included RIC pr target in GitHub action and removed the building commands that were already there since the pr target would also build them and would generate conflicts
  • Removed unnecessary -it option from codebuild_build.sh because it was causing tty error when running the GitHub action
  • Refactored a test that uses a special character to expect failure if the encoding is not set to UTF
  • Updated to CentOS:7
  • Removed CentOS:6 from the OS compatibility test since it reached EOL

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Copy link

@edhzsz edhzsz left a comment

Choose a reason for hiding this comment

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

LGTM!

@carlzogh carlzogh self-requested a review December 4, 2020 16:16
Comment on lines +35 to +38
# Test Runtime Interface Client
- name: Run 'pr' target
working-directory: ./aws-lambda-java-runtime-interface-client
run: make pr
Copy link
Contributor

@carlzogh carlzogh Dec 4, 2020

Choose a reason for hiding this comment

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

Looks like this actually takes a while - I suggest we create a separate workflow that would only trigger if changes were made for the RIC (aws-lambda-java-runtime-interface-client).

ref. https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#example-including-paths

Copy link
Contributor

Choose a reason for hiding this comment

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

We could even take the opportunity to define a workflow per package as there is probably no need to build them all on every change.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Creating a follow up PR for restructuring the workflow.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sounds good!

@carlzogh carlzogh merged commit 4a434e4 into aws:master Dec 4, 2020
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