Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Improve the FORCE_QUEUE process in Helix-machines

See original GitHub issue
  • This issue is blocking
  • This issue is causing unreasonable pain

By default, PRs to helix-machines will only attempt to generate images for a single windows and a single linux queue. This is often not enough testing for some of the changes to machine configurations, which have different subtleties depending on the OS and version.

We have the FORCE_QUEUE feature that allows to generate specific images during the PR process. However, this feature is sometimes not used, and we end up having to revert changes that fail in specific OSes that weren’t tested during the PR.

We should look into ways of making the FORCE_QUEUE feature more visible, so that both PR authors and code reviewers are more easily aware of any gaps in their testing.

Release Note Category

  • Feature changes/additions
  • Bug fixes
  • Internal Infrastructure Improvements

Release Note Description

For internal use only…

We have removed default queues and tightened the FORCE_QUEUE logic. Specifically:

  • build only FORCE_QUEUE images in PR builds
    • avoid complications like checking for other queues in the same OS group
    • those checks previously chose the first Linux and Windows definitions found as defaults
  • require at least two FORCE_QUEUEs in PR and manual builds
    • named queues must exist and require distinct images
  • support BUILD_EXISTING_IMAGES in commit descriptions to force rebuilds
  • add words to the PR template (when targeting ‘main’) about how to use FORCE_QUEUE and BUILD_EXISTING_IMAGES
  • refactor some of the CreateCustomImage code; change logging and comments

Issue Analytics

  • State:closed
  • Created 5 months ago
  • Comments:11 (11 by maintainers)

github_iconTop GitHub Comments

chcostacommented, Jun 1, 2023

@riarenas - just a note, so we don’t forget our hallway conversation : consider removing default queues (just make them suggestions) so people are forced to be intentional about which queues are running (require at least one queue [maybe more]) be defined.

dougbucommented, Jun 27, 2023

Builds of main are no longer showing ill effects of the fix. Closing this issue. If necessary, we’ll track the latest build break (which might just require a few more retries0 in a new issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Configuring queues - Documentation for BMC Helix ...
To configure queues · Click the Remedyforce Administration tab. · On the Home page, click the Manage Users tile, and from the menu,...
Read more >
Managing queues availability and assignment
From the Queues for list, select the object whose queue you want to assign. The options that you select in the Configure Queue...
Read more >
Upgrade Swarm
Swarm upgrade process: If you installed Swarm via a package, see Upgrade a Swarm package installation for details. If you installed Swarm via...
Read more >
How to Create and Configure a Queue in BMC ... - YouTube
How to Create and Configure a Queue in BMC Helix Remedyforce. ... How to Increase the Display Limit in Self Service Lookup Fields....
Read more >
Processing specific job classes
GitLab has two options for creating Sidekiq processes that only handle specific job classes: Routing rules are used on
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found