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

AY-6885_Perforce events to AYON #18

Open
ynbot opened this issue Oct 29, 2024 · 0 comments
Open

AY-6885_Perforce events to AYON #18

ynbot opened this issue Oct 29, 2024 · 0 comments
Assignees
Labels
sponsored This is directly sponsored by a client or community member type: feature Adding something new and exciting to the product

Comments

@ynbot
Copy link

ynbot commented Oct 29, 2024

For further automations, we need to be able to get events (like commits, etc) from Perforce and get them to AYON events so we can act on them.

Summary:
We need to create AYON endpoint that will receive messages for a trigger script and convert them to AYON events. This endpoint should live on some AYON addon (and most likely ayon-version-control (and we should rename that one to ayon-perforce or ayon-helix-core)). This endpoint will "just" create event, it shouldn't process anything (like getting files from the changelist number passed in the event, etc. - that should be job of other parts).

About triggers:
In Perforce we can utilize Triggers - Triggers are scripts running on the server side, either writen in Python, Ruby, Perl or Bash, listening to specific events.

There are many events available, but for our use case, we want to handle change-commit that executes after changelist creation, file transfer, and changelist commit (example of change-commit trigger is here). This will trigger on commit, but maybe we want to handle when the data is actually shared. Perforce has push
and submit. There are differences, most notable is that push can work with multiple changelists - push-commit is the name of event. For auditing, we might want to handle fetch event.

When this trigger script is added to perforce and registered in trigger table, it communicates with the server via script variables. We can use %changelist% to get the number of newly submitted changelist to query server for the list of changed files and with that, we can find out what asset was changed. Note that you can use p4 command directly in trigger scripts.

This issue was automatically created from Clickup ticket AY-6885

@ynbot ynbot added sponsored This is directly sponsored by a client or community member type: feature Adding something new and exciting to the product labels Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sponsored This is directly sponsored by a client or community member type: feature Adding something new and exciting to the product
Projects
None yet
Development

No branches or pull requests

2 participants