Skip to content
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

CI: Implement GitHub action cache in pull-request-management workflow (WORK IN PROGRESS) #4778

Closed

Conversation

Shivani-gslab
Copy link
Contributor

@Shivani-gslab Shivani-gslab commented Dec 3, 2024

Change Summary

WORK IN PROGRESS
Implementing github action cache for pull-request-management workflow.

Testing multiple approaches here -

Points to be tested -

Related Issue(s)

Fixes #

Component(s) name

arista.avd.<role-name>

Proposed changes

How to test

Checklist

User Checklist

  • N/A

Repository Checklist

  • My code has been rebased from devel before I start
  • I have read the CONTRIBUTING document.
  • My change requires a change to the documentation and documentation have been updated accordingly.
  • I have updated molecule CI testing accordingly. (check the box if not applicable)

Copy link

github-actions bot commented Dec 3, 2024

Review docs on Read the Docs

To test this pull request:

# Create virtual environment for this testing below the current directory
python -m venv test-avd-pr-4778
# Activate the virtual environment
source test-avd-pr-4778/bin/activate
# Install all requirements including PyAVD
pip install "pyavd[ansible] @ git+https://github.com/Shivani-gslab/avd.git@github_cache_tests#subdirectory=python-avd" --force
# Point Ansible collections path to the Python virtual environment
export ANSIBLE_COLLECTIONS_PATH=$VIRTUAL_ENV/ansible_collections
# Install Ansible collection
ansible-galaxy collection install git+https://github.com/Shivani-gslab/avd.git#/ansible_collections/arista/avd/,github_cache_tests --force
# Optional: Install AVD examples
cd test-avd-pr-4778
ansible-playbook arista.avd.install_examples

@github-actions github-actions bot added the type: code quality CI and development toolset label Dec 3, 2024
@Shivani-gslab Shivani-gslab force-pushed the github_cache_tests branch 4 times, most recently from 577ca00 to 4adc10e Compare December 6, 2024 06:55
@github-actions github-actions bot added the state: conflict PR with conflict label Dec 9, 2024
Copy link

github-actions bot commented Dec 9, 2024

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot removed the state: conflict PR with conflict label Dec 10, 2024
Copy link

Conflicts have been resolved. A maintainer will review the pull request shortly.

@github-actions github-actions bot added the state: conflict PR with conflict label Dec 12, 2024
Copy link

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot added the state: conflict PR with conflict label Dec 20, 2024
Copy link

This pull request has conflicts, please resolve those before we can evaluate the pull request.

Copy link

Conflicts have been resolved. A maintainer will review the pull request shortly.

@github-actions github-actions bot removed the state: conflict PR with conflict label Dec 23, 2024
@Shivani-gslab Shivani-gslab force-pushed the github_cache_tests branch 2 times, most recently from 3dbeea2 to 7cb6f37 Compare December 23, 2024 07:54
@github-actions github-actions bot added the state: conflict PR with conflict label Jan 14, 2025
Copy link

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@gmuloc
Copy link
Contributor

gmuloc commented Jan 20, 2025

closing in favor of #4870 - interesting to check caching of artefacts.

@gmuloc gmuloc closed this Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state: conflict PR with conflict type: code quality CI and development toolset
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants