Automatic Build Archival on Issue Completion
Completed issues need their builds archived. Do it automatically instead of remembering to grab artifacts later.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Get Build Artifacts
Tool to get the list of artifacts for a specific build job. use when you need to retrieve artifacts after a job completes.
Why this helps
Closing issues means remembering to save their build artifacts. It's easy to forget, then later you can't find the exact build that fixed something.
- Never lose build history for completed work
- Reduce manual archival steps
- Keep complete deployment traceability
Setup
Build it in a few focused steps.
- 1Connect Appveyor to Notis
- 2Ask Notis: 'When an issue is marked completed, fetch its build artifacts and add them to a record for this issue'
- 3Select 'Issue Updated' as your trigger - fires when status changes
- 4Pick your docs or archive channel
- 5Test by marking an issue complete and verifying artifacts are captured
Questions about this workflow
What if an issue doesn't have a build?
Notis will fetch the list but it might be empty. That's fine - better than forgetting to check.
Can this archive other information too?
Yes. Extend it to capture description, assignee, and timestamps for a complete archive record.
How long should we keep archives?
That's your call. Use a cron automation to clean up old archives monthly, or keep forever for compliance.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Appveyor. A trigger fires from one place; an action lands in another.
Linear triggers
Appveyor actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Build Artifacts
Tool to get the list of artifacts for a specific build job. use when you need to retrieve artifacts after a job completes.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Environments
Tool to get a list of all deployment environments. use when you need to enumerate available environments before creating deployments.
Comment Received Trigger
Triggered when a comment is received.
Get Projects
Tool to get a list of all projects for the authenticated account. use after authentication to enumerate available projects.
Issue Created Trigger
Triggered when a new issue is created.
Get Role
Tool to retrieve details of a specific role. use when you need to inspect permissions and metadata of a role by id.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get Roles
Tool to retrieve all roles in the account. use when you need to enumerate available roles before assigning permissions.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Get Users
Tool to retrieve all users in the account. use when you need to list all team users in your appveyor account.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Appveyor, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Appveyor.