v6.8.4

v6.8.4 Release Notes

Release Date

Thursday, Sep 13 2018

Features

• Excluded branches can be run manually: CI branches that do not run for webhooks because of a branches setting in shippable.yml can now be run manually. To do so, click the play button on the project dashboard and select the branch.
• Drydock update: Updating all Shippable official images with latest
  stable versions of languages, cli's and services. Refer to documentation
  for v6.8.4 for details.
• Updated AWS SDK in deploy jobs: Deploy jobs in Shippable Assembly Lines now use a more recent version of the AWS SDK, with support for healthCheck in task definitions.
• shipctl notify support for IRC and Windows: shipctl notify can now be used with IRC notification resources, and is also fully supported on Windows nodes. See shipctl documentation for more details.
• Enhanced console log handling: The enhanced, non-blocking approach towards handling console logs will now be the default handler instead of being opt-in. You can expect an improvement in the stability and speed of your builds, especially if it produces a significant amount of console logs.
• Enhanced Release notes: Now the latest 10 release notes are available at https://app.shippable.com/changelog, this can be accessed by clicking the newspaper icon on the top right of the app
• Environment variables in grid view: Now you can view environment variables in grid view of subscription, custom, project and job dashboard. For that, you need to enter ENV vars matching keys in show ENVs in grid view field, the project settings and job config pages have this option.
• New tab layout for navigation in dashboards: Now all the views in subscriptions, custom, project and jobs dashboards can easily be accessed through tabs
• Added support for latest docker: BYON nodes on Windows Server 2016 can be initialized with Docker 18.03.1-ee-3

Fixes

• timeTriggers for runCI: timeTrigger resources will now properly trigger runCI jobs.
• Fixes issue of several node pool's node limit getting reset to 0: node limit field of node pools having admin addons will no longer incorrectly reset to 0 on any change in subscription's licenses.
• Fixes issue of method required for notification type resource in yml builder Fixed notification type resource in yml builder, method field is not required for slack and hipchat.
• Editing params from SPOG: Editing a params resource directly from SPOG will now correctly save.
• Fixes reinitialize button for manually initialized nodes: Clicking reinitialize on view node pool page for manually initialized nodes will now show a button to download the init script.
• Fixes gitRepo webhook not setup error in assembly lines: When the webhook creation fails, rSync job logs will show the error cleanly.
• Fixes gitRepo branch names changing behind the scenes: Fixed gitRepo branch names changing due to incorrect webhook checks. Now, gitRepo trigger subsequent jobs on recieving webhook.
  (support#4537) (support#4553)

Shippable Server

• Features
  • simple title: brief description
• Fixes
  • Public Bitbucket projects inaccessible: Users were not able to view public projects on Bitbucket Cloud without logging in. This has been fixed so that users must be logged in to view private projects or projects on private git servers but not public projects on the cloud versions of Bitbucket, GitHub, or GitLab.
  • UTF-8 handling in BitBucket Server add-on: The shippable-integration-bbs add-on has been updated to send UTF-8 payloads. This fixes problems with character encoding for non-ASCII data.
  • Fixes email service crashing: On upgrading shippable version from v6.4.2 or less, queued emails will get successfully processed.

History

To view Shippable's release history, check out our releases page on github.

v6.8.1

v6.8.1 Release Notes

Release Date

Monday, Aug 27 2018

Features

• More node statistics: Node statistics are collected more frequently and the number of Docker containers and images on a node is now displayed on the node page. Existing nodes will need to be reinitialized in order to show the image count, but reinitialization is not required to continue to use older nodes.
• Ability to re-initialize the node in nodepool list page: Nodes can now be re-initialized from the node pool page instead of having to go to the node's detail page.
• shipctl notify: Custom notifications can be sent to Slack or webhooks using shipctl. Custom nodes will need to be reinitialized to use this feature and Windows is not yet supported. More information is available in the shipctl documentation.
• Added support for latest docker: BYON nodes on Ubuntu 14.04, Ubuntu 16.04(x86_64), CentOS 7 and RHEL 7 can be initialized with docker 18.03.01-ce
• Unified webhook and access key per repository: CI and pipeline will now use only single webhook and access key per repository instead of different webhooks and access keys for different resources. The existing pipeline resources will be migrated to use the unified webhooks automatically once you run your rSync jobs.
• Added support for depth & gitConfig settings in CI: Now CI repos can be shallow cloned by specifying certain depth. Git config can also be done before the repository is cloned.
• Added support for depth & gitConfig settings in gitRepo: Now gitRepos can be shallow cloned by specifying certain depth. Git config can also be done before the repository is cloned.

Fixes

• Cleanup credentials before and after the CI build: Credentials used in the CI builds will get cleaned up from the build agent before and after the CI build is run.
• Default notification settings with slackKey: The correct default settings are used when type: slackKey is specified in a CI shippable.yml.
• Reduce overhead of artifact copies in rerun failed only jobs: Instead of duplicating consoles, tests, and coverage, we will now reference the original data when loading a rerun failed only matrix item that was previously successful.

Shippable Server

• Features
  • Updated default docker version for installation on Ubuntu 14.04: Server installations of both onebox and multi node types on Ubuntu 14.04 now use docker 18.03.01-ce
  • Updated default docker version for installation on Ubuntu 16.04: Server installations of both onebox and multi node types on Ubuntu 16.04 now use docker 18.03.01-ce
  • Updated default docker version for installation on CentOS 7: Server installations of both onebox and multi node types on CentOS 7 now use docker 18.03.01-ce
• Fixes
  • Slack notifications with type: slack: Specifying type: slack was not working with newer Slack integrations in some installations. Both slack and slackKeys will now work as intended.

History

To view Shippable's release history, check out our releases page on github.

v6.7.4

v6.7.4 Release Notes

Release Date

Tuesday, Aug 07 2018

Features

• SPOG subscription level object limit: Subscription administrators can now set a limit to the number of objects that can be displayed in the SPOG view for that subscription, this can be used to prevent users from accidentally loading the full SPOG which will be helpful for subscriptions with a very large number of resources/jobs in them which will possibly create browser performance issues.
  this setting can be found in the subscription settings page with the title SPOG Object Limit.
• Ability to create subscription owned integrations: Subscription users can now create shared subscription integrations, which allows you to restrict the usage of integration to members, collaborators and admin based on your requirement. This feature requires v6.7.4 of the build runner. BYON nodes will need to be reinitialized if they are running older versions. Customers running on-demand nodes with caching will need to stop their cached nodes to get the latest version of the build runner.
  (support#4128)
• Ability to use integrations directly to runSh jobs: Integrations can be directly added to runSh jobs without creating the integration resources. (Docs)
• Drydock update: Updating all Shippable official images with latest
  stable versions of languages, cli's and services. Refer to documentation
  for v6.7.4 for details.

Fixes

• Improve TASK validation for rSync: rSync now catches indentation and data type errors for script, nodePool, env and timeoutMinutes in the TASK section of a runSh's YML.
• shipctl get_integration_resource_field: Avoids unexpected error in get_integration_resource_field command, when the resource name is invalid (support#4472)
• Pull Request for private Bitbucket gitRepo: runSh job running on Windows Server 2016 node is able to fetch the Pull Request content in case of Bitbucket gitRepo resources.
• Switching between SKU's flow is not correctly handled: Refines the proration logic correctly to avoid charging additional amount while switching SKUs. (support#4448)
• Subscription licenses not updated if node pool deletion fails: Now subscription licenses get updated on a successful transaction even if any node pool(s) didn't get deleted or updated due to some reason. (support#4475)
• Modern SPOG disabled links: disabled links (dotted lines) in modern SPOG will be displayed correctly wherever necessary.
• Ruby builds fail when all steps succeed: added fix to make sure ruby build scripts exit with proper exit code on runtime versions v6.6.1 and above. (support#4297)

Shippable Server

• Features
  • Onebox auto-recovery on reboots: Shippable Onebox installations will auto recover all services when the Control
    Plane server reboots. Users can now shutdown the hosts when not in use to cut down costs for their pilot installations.
  • Docker builds on restricted shared nodepools: Docker builds are supported on restricted shared nodepools. With this, users will be able to use docker capabilities on the restricted shared nodepools.

History

To view Shippable's release history, check out our releases page on github.

v6.6.1

Release Notes

Release Date

Wednesday, Jun 13 2018

Features

• yml templates: runSh jobs now support yml templating. See the docs for more details.

Fixes

• streaming logs: Fixed a bug in log streaming that caused the browser to slow down in some cases.
• cached nodes: Fixed a bug where cached nodes would be terminated after changing runtime versions before a new job would run.
• dynamic node disks: Fixed a bug that was causing the wrong type of storage to be attached to dynamic nodes, impacting read/write performance.

Shippable Server

• Fixes
  • superuser access: Superusers should no longer have trouble loading user pages.

History

To view Shippable's release history, check out our releases page on github.

v6.5.4

v6.5.4 Release Notes

Release Date

Thursday, Jun 07 2018

Features

• Dry Run YML Builder: The Dry Run feature has been enhanced to include the ability to build the Assembly Line YML from scratch. See the docs for more details.
• Saving OUT resource during failure: A new flag on_failure: true can be added to OUT resources for cases when you want a version of the resource to be created even if the job fails. see docs for a description
• Integrations for public projects: Used to be blocked on all PRs, but now will be used when the PR is coming from an internal branch.
• Rerun pull request sha selections: A pull request rerun now gives the user the option to run against the original base sha instead of latest sha.

Fixes

• Node Cluster integration: Adding a Node Cluster account integration will no longer produce an error.
• YML block notation logging: Extra logs that were present due to yml block notation have been removed. The output should look similar to single line statements now.
• Postgres service sleep: Postgres will no longer arbitrarily sleep for 30 seconds before stopping.
• Windows shipctl replace: This now supports replacing environment variables that use the braces format ``. Other operating systems already have this functionality.
• Windows shipctl copy: The shipctl copy_file_to_state utility now works properly on windows hosts.
• Payloads not saved on failure: When a custom webhook payload is sent on failure, it will now properly contain the desired values.
• Queued status for gitRepo: Jobs with gitRepo IN resources that are using the showBuildStatus: true option will now correctly post their queued status to the provider.

Shippable Server

• Features
  • Account sync disabling: Server admins can now choose to disable automatic account sync.
    • Only the projects specifically added by the user will be present on Shippable.
    • Each user must manually add the projects that they want to use.
• Fixes
  • SuperUser trigger from SPOG: Jobs can now be triggered from SPOG by system superUsers regardless of project permissions.

History

To view Shippable's release history, check out our releases page on github.

v6.5.1

v6.5.1 Release Notes

Release Date

Thursday, May 24 2018

Features

• Node caching: Node caching is a premium feature that can be purchased for any on-demand Node SKU for an additional price of $25/node per month. If turned on, your build nodes (minions) will be paused between jobs instead of being terminated and spun up again. This will not only save node spin up time, but any dependencies or Docker images you pulled for your CI or CD workflows will be available on your nodes.

  Node caching is most useful for customers taking the following actions as part of their CI/CD workflows:

  • Using a custom Docker image
  • Pulling a Docker image
  • Building a Docker image
  • Pulling large dependencies which don't change for every job

• Retrying failed matrix builds: If you have a CI workflow that leverages matrix builds, you might have one or two jobs in the matrix that fail due to a non-code related temporary reason, such as a network glitch, npm mirrors being down, etc. In these cases, you want to retry the failed jobs, but not necessarily the jobs that succeeded. The new Retry failed jobs option will let you do exactly that!

  To make things clear, say you have a build matrix of 5. For build # 450, you see that 450.3 and 450.4 failed, while 450.1, 450.2, and 450.5 succeeded. You click on Rerun failed jobs for build #450.

  Here is what happens:

  • A new build is spun up, let us assume it is 451.
  • All jobs that were successful (450.1, 450.2, 450.5) are simply copied over to the new build, as 451.1, 451.2, 451.5, along with their status.
  • All failing jobs (451.3, 451.4) are queued to be run again.
  • Build status for 451 is the aggregate of the jobs that were copied over plus the jobs that were run again.
  • The new build will be clearly marked as a re-run of the original build.
  • If 450 was a pull request, build #451 will overwrite the pull request status in your source control provider

  While this is immensely useful and saves time for large matrix builds, there is one small caveat. If some time passes between the original build and the rerun, the successful status for the copied over jobs might no longer be valid due to merges and other changes that might happen in that time. So if you choose to rerun only failed jobs, you might have a false sense of security. For this reason, we recommend that if a bunch of code has changed since the original build, you should rerun the whole build instead of only failed jobs.

• SPOG UX improvements:

  • We have removed the on-hover popup for jobs and resources. Users gave us feedback that it often comes in the way when they wanted to right click on the SPOG.
  • We have implemented a compact context menu that includes all the actions that are present in the current context menu and also shows all of the information that is being shown in the on-hover popup.

• Current AMI version is exposed as an environment variable: Using the current AMI version while pulling a shippable language image in a runSh or runCI job speeds up the execution of the job tremendously since the docker image is already available on the node. The current AMI version can be consumed as an environment variable.

  jobs:
  - name: container_custom_image
    type: runSh
    steps:
      - TASK:
          name: custom_container_opts
          runtime:
            options:
              imageName: drydock/u14pytall
              imageTag: ${SHIPPABLE_AMI_VERSION}
              options: --dns=4.4.4.4 --dns=8.8.8.8
          script:
            - echo "Checking runtime values"
            - sudo docker info

• Enhanced shipctl to add semantic version bump functionality: We implemented a new shipctl function bump_version that can take in a semantic version string, as well as a bump type, and return the resulting string from taking the appropriate bump action on the supplied version.

    NEW_VERSION=$(shipctl bump_version v1.0.0 minor)
    echo ""
    -> v1.1.0
  
    FINAL_VERSION=$(shipctl bump_version v1.2.3-rc.5 final)
    echo ""
    -> v1.2.3

• Allow for custom incoming webhooks to trigger pipeline jobs: User have asked for the ability to receive webhooks from an external service, like Quay.io, to trigger a pipeline job. Today onwards, you can add a webhook resource type in your shippable yml and specify it as an input to any of your jobs.

  For more information on how to create this resource and specify it in your provider, please go here.

Fixes

• An invalid payload sent to the POST route of accountIntegration was throwing an uncaught exception. This has been fixed.
• An invalid credit card specified in the Billing page does not show a migration in progress panel. This error is gracefully handled and users are able to continue to use the billing page to retry their last operation.
• Version names do not overflow in job consoles page.
• Free users can change their addon type's from On-Demand to BYON and vice-versa for a single node without adding a card.
• The subscription node pools page auto refreshes in real time for any changes to on-demand node pools.
• The tooltip is rendered correctly on hover over any flags in the Flags dropdown.
• Build runs on public projects are visible to users who do not have a shippable account.
• Rendering of long job names in the SPOG view has been improved.
• Users can switch to all supported java versions in their Node pool runtime version by using the shipctl command pre-installed in their language image.
• When users upgrade/downgrade their plan without changing the on-demand SKU, the runtime version for all existing node pools is not unaffected. In addition, when users buy multiple SKU's (on-demand and/or BYON), the new node pools will have latest runtime version automatically set. This will make new builds work seamlessly without needing any user invention to manually set the runtime version.
• Manually triggered runCI jobs set triggeredBy correctly.
• Paring secure environment variables that contain special characters like = works as expected.

Custom Nodes

• Windows custom node initialization failure has been fixed on Nodes that do not have Docker preinstalled.

Shippable Server

• Fixes
  • Users can run Admiral CLI without manually installing any dependent packages.
  • The Admin subscriptions page renders correctly (does not hang) and with paging for installations with a very large number of subscriptions.

History

To view Shippable's release history, check out our releases page on github.

v6.4.4

v6.4.4 Release Notes

Release Date

Monday, Apr 30 2018

Features

• Failure logs in email notifications: Email notifications for both CI and Assembly Lines can be configured to include log output of failing commands with the sendFailingSnippet option. To enable this, see the CI email or Assembly Lines configuration documentation.

Fixes

• Listing a webhook subscription integration with no linked account integration in a CI shippable.yml now creates a run with the same error message as other integration types.
• Docker integrations will now properly log in on Ubuntu 16.04 and CentOS 7 dynamic nodes.
• Job names in SPOG will wrap to a second line if space is available.
• Fixed a crash in the internal "sync" service.
• New NOTIFY line syntax in pipeline jobs will now properly trigger the notification workflow.
• on_success webhook logs will no longer be cut off by the log archiving service.
• When searching SPOG for a particular job, if that job is stale, the search highlight will take priority over the stale highlight.
• When a build's webhook payload fails to send due to a parsing error, a helpful message will be displayed in the logs.

Custom Nodes

• Node status updated when nodes do not report a status: If a node has not sent updated node statistics for 15 minutes (configurable in Shippable Server installations), the node status will be updated to failed and jobs will not be queued for that node.

Shippable Server

• Features

  • Admiral UI usability enhancements
    • User can now click the header of each panel to expand/contract, not just the arrow.
    • URL update panel will stay open after editing, so the change can be easily seen.
    • Node pool configuration has been split into multiple panels.
    • Refreshing the page will maintain the currently selected tab.
    • Default System Machine Image (SMI) will be the current Admiral release that was installed instead of "master".
    • Updated naming conventions for nodes to match latest standards.
    • Included various spelling corrections.
    • The SMI table is now searchable.
    • SubnetID for SMI will now properly save on initial creation.
    • Redundant fields are removed from the SMI table.
    • Buttons will be disabled while "apply" action is in progress.
  • Admin page enhancements
    • Added an insights section to the "Analytics" tab of the admin page.
    • Subscription page has been enhanced in several ways
      • Up to 25 subscriptions shown immediately by default
      • Licenses list truncated to 1 by default, with a "show more" button to view details.
      • "isPaid" column has been removed
    • Accounts page has been enhanced in several ways
      • Added a summary panel at the top, showing total active accounts, and further dividing them between those with "read-only" access to projects vs "full" (has write access to at least 1 project).
      • "Subscriptions" column restricted to a single line with a "more" button to show all subscriptions that the account can access.
      • "Enabled Projects" column restricted to a single line with a "more" button to show all enabled projects that the account can access.
      • Search box will cover name, email, and ID instead of having to select one option.
  • Addons are enabled by default in fresh installation of Shippable - After a fresh installation of Shippable, the following Addons will be enabled by default.
    • AWS Keys
    • Azure DC/OS
    • Azure Keys
    • Node Cluster
    • Docker Cloud
    • Docker DataCenter
    • Kubernetes
    • Joyent Triton
    • Digital Ocean
    • Google Cloud
    • Webhook
    • HipChat
    • Slack
    • Jira
    • AWS Keys (ECR)
    • JFrog Artifactory
    • Quay.io
    • Docker Registry
    • PEM Key
    • Key-Value pair
    • Git Credential

• Fixes

  • Master integration validation: When adding system integrations, all included fields must have corresponding fields in the master integration in order to pass validation.
  • Docker upgrade during install: When installing Admiral, the host machine will be upgraded to Docker 17.06 if possible.

History

To view Shippable's release history, check out our releases page on github.

v6.4.2

v6.4.2 Release Notes

Release Date

Friday, Apr 13 2018

Features

• UX improvement for Node Pools: While creating or editing a node pool, the Runtime versions dropdown is sorted in descending order.
• CI jobs in Assembly lines render YML: You can view the complete YML for a CI job used in an Assembly Line.
• Fine grain control on replication of a gitRepo resource: A common use case is to trigger a managed deploy job or runSh after CI in an Assembly line, using the same branch and SHA as CI using the replicate feature. Customers often want to trigger CI for PRs but they do not want their managed and unmanaged jobs downstream to be triggered for PRs. You can enable this scenario by specifying replicateOnPullRequest: false.

jobs:
  - name: myrepo_runCI
    type: runCI
    steps:
      - OUT: myGitRepoResource
        replicate: myrepo_ciRepo
        replicateOnPullRequest: false

• Added support to deploy job for forced deployment with release inputs
  • Consider the following assembly line: image->manifest->release->deploy. In the deploy job, you can now attach force: true to the release IN step and the deploy job will deploy the manifests in your release, regardless of whether or not they have changed since the previous deployment.
• Added support to trigger downstream jobs even if an upstream job fails
  • new IN step modifier flag: triggerOnSuccess (defaults to true) can be set to false if you do not want the job to be triggered as a result of a successful completion of the IN job.
  • new IN step modifier flag: triggerOnFailure (defaults to false) can be set to true if you want the job to be triggered even when the IN step has failed.

jobs:
  - name: deprovision
    type: runSh
    steps:
      - IN: test_job
        triggerOnFailure: true  (default false)
        triggerOnSuccess: true  (default true)

• Added native support for Amazon ECS auto scaling in managed deploy jobs
  • enhanced replicas resource that allows you to create scaling policies and CloudWatch alarms for a particular manifest.
  • see docs on replicas and deploy jobs to utilize this feature.

Fixes

• Mismatched ssh-agent versions in custom build images will no longer result in build failure.
• Navigation from a Shared view to another works as expected.
• After a CI build completes, its status is reflected correctly in the Latest Status grid.
• SSH access to Ubuntu 16.04 nodes for debug CI runs works as expected.
• Running a Jenkins CI job, using an external CI integration, triggers downstream jobs which have the external CI job as an IN.
• Updating billing details without a change in total cost is allowed.
• Jira issue created for a non-matrix CI builds create issue links in the CI build console page immediately.
• UX issues for Subscription and Project Insights have been fixed for Chrome on OSX.

Shippable Server

• Custom webhook integrations can now be properly utilized.

History

To view Shippable's release history, check out our releases page on github.

v6.3.4

v6.3.4 Release Notes

Release Date

Friday, Mar 30 2018

Features

• On-demand nodes for Ubuntu 16.04, Windows Server 2016 and CentOS 7: You can now purchase on-demand SKU's for Ubuntu 16.04, Windows Server 2016, and CentOS 7.

• Integration with JIRA: You can create tickets in JIRA directly from the runSh and runCI job console dashboard. A JIRA integration allows you to specify your JIRA Server URL, username and token. Thereafter, with a single click in your job console page, you can create a story/task/bug type of issue for any of your projects and also attach the console logs.

• Setting priority on runSh and runCI jobs: You can now set priority on runSh and runCI jobs. This may be set to any value from 0 to 10000 inclusive, with 0 being the highest priority and 10000 being the lowest priority.

  • All jobs will have default priority as 9999.
  • All waiting jobs will be sorted first according to creation time and then by priority before being queued.
  • Example:

    name: test_features
    type: runSh
    priority: 100
    steps:
      - IN: features_repo
      - script: echo "executing job"
    

• Adjustable custom node disk usage limit: You can now define a maximum disk usage limit for all nodes in a subscription node pool from the subscription node pools page, for both subscription node pools and system node pools (for server admins).

  • A default of 90% maximum disk usage limit will be applied if none is specified.
  • Disk usage limits can be specified per Node pool.

• Manually triggered jobs in the SPOG can be easily found: The SPOG renders jobs which need to be manually triggered with a dark gray border, when an update to any of its input occurs. This allows you to quickly scan the SPOG and find jobs that need to be manually triggered. Manually triggered jobs have switch: off applied to one or more of their inputs. Triggering the job resets the border.

• Search jobs and resources in the SPOG: You can search for jobs and resources in the SPOG by either clicking on the search icon on the top-right corner in the SPOG view or by using the keyboard shortcut ctrl + space. This opens a search box which has intellisense allowing you to quickly select the jobs/resources you want to view. Once a selection is made, the target is brought into focus and highlighted with a yellow border.

Fixes

• Fixed job triggering issues
  • Soft-deleted jobs will no longer prevent connected jobs from automatically triggering.
  • runSh jobs are no longer serialized when the parent syncRepo is serialized in CI.

Shippable Server

• Shippable Server UX has been significantly improved. Configuration has been cleanly separated into Control and Build planes and we have added support for Onebox installation.

• Bitbucket Sever OAUTH plugin works correctly in a proxy environment. Assuming the Bitbucket Server is running on bbs.example.com, the proxy could be configured to reject requests for this URL because the traffic is meant to be routed locally. Users can now add bbs.example.com to the no_proxy setting when prompted by Admiral.

History

To view Shippable's release history, check out our releases page on github.

v6.3.3

v6.3.3 Release Notes

Release Date

Thursday, Mar 22 2018

Features

• Improved usability of the Nodes dashboard: You can see the OS and architecture of your nodes when you click on any node in the Node pool.
• Ability to specify timeout for runCI and runSh jobs: You can specify the timeout of your runSh jobs in yml or Shippable UI. In the UI, timeout can be specified at the Node pool or Subscription level in the Node pool or Subscription settings respectively. Please read the runSh documentation on timeoutMinutes for more inforamtion on how to specify the timeout in your yml file.
• Analytics update: We have made a significant update to analytics.
  • The Subscriptions insights page renders a bar graph of all builds across the sub in the last 7 days with height of the bar as the duration and the color of the bar as status.
  • The Subscription insights page renders a stacked area chart plotted by days for last 7 days with each colour representing each status, the height representing the number of builds with that status and the total height representing the total builds for that day. A dropdown allows you to filter by job type such as runSh, runCI, deploy etc.
  • The Subscription insights page renders a line graph of median, Avg, min and max total durations for each day for the last 7 days. A dropdown allows you to filter by status and another dropdown allows you to filter by job type.
  • The Subscription insights page renders the queue count of jobs and processing count of jobs by minute for the last 7 days.
  • The CI job insights page renders a bar graph of builds in the last 7 days with height of the bar as the duration and the color of the bar as status.
  • The CI job insights page renders a line graph of median, min and max test results for each day for the last 7 days for passed, failed and skipped categories.
  • The CI job insights page renders a line graph of median and max total coverage for each day for the last 7 days.
  • The CI job insights page renders a line graph of median, avg, min and max total durations for each day for the last 7 days. A dropdown allows you to filter by status.
  • The CI job insights page renders a stacked area chart plotted by days for last 7 days with each colour representing each status, the height representing the number of builds with that status and the total height representing the total builds for that day.
  • All Job insights pages renders a stacked area chart plotted by days for last 7 days with each colour representing each status, the height representing the number of builds with that status and the total height representing the total builds for that day.
  • All Job insights pages render a bar graph of builds in the last 7 days with height of the bar as the duration and the color of the bar as status.
  • All job insights pages renders a line graph of median, Avg, min and max total durations for each day for the last 7 days. A dropdown allows you to filter by status.
• Ability to edit params resources from the SPOG: Right click on the params resource in the SPOG and click on Update to edit the values of any params .
• Improve Usability of Console logs: Console logs have been grouped into a reduced number of sections so that users can quickly drill down to the specific log they are interested in.
• Improvements to Windows BYON nodes initialization: Windows nodes can be initialized without needing to download any external utilities and without requiring any environment variables to be set.

Fixes

• When deploy jobs are removed from the yml, the services that they deployed are deleted automatically.
• When a soft deleted syncRepo is restored from the UI, all the jobs and resources created by the syncRepo are correctly restored.
• The DELETE method on the /resources route works as expected.
• Failures in tarring Code coverage output files have been fixed.
• Upgrade deployments on ECS correctly set the replica count if the image applied to the Load balancer resource changes.
• Matrix jobs correctly trigger OUT variables.

Shippable Server

• Shippable Server can be installed on Ubuntu 16.04 LTS: Both one-box and multiple-server configurations are supported on Ubuntu 16.04 LTS.
• Shippable Server allows specification of HTTP proxy servers: Admiral downloads artifcats and packages needed for install using the HTTP protocol. If your corporate intranet routes HTTP traffic using a proxy, you can specify the proxy in Admiral UI.
• Support for public GIT repos for GitHub Enterprise: Public gitRepo's can be specified as an input for runSh/runCLI jobs.

History

To view Shippable's release history, check out our releases page on github.