IFS Cloud Build Place administration

← All services

In IFS Cloud, your own solution (your modifications, reports and integration code) lives in the Build Place. It holds your customer solution repository, runs the builds, and produces the deliveries that are deployed to your environments through IFS Lifecycle Experience. Under the evergreen model it is in use every time you take a service update or a release, not only during an implementation, so it needs looking after continuously.

What we look after

• Your customer solution. Repository structure, branches aligned to the IFS Cloud version you run, and a clean history of what changed and why.
• Builds. Running and monitoring builds, and diagnosing and fixing failed ones quickly.
• Deliveries and deployments. Creating deliveries and deploying them through your environment landscape, from development and test to production, in a controlled order.
• Service updates and releases. Bringing your solution up to each new IFS service update or release, resolving conflicts with your modifications, rebuilding and redeploying. See IFS Cloud service updates and releases.
• Environments. Housekeeping across your environment landscape, including refreshes and copies so test environments stay representative.
• People and access. Onboarding developers and partners, keeping access appropriate, and documenting how your Build Place is organised.

Ways to work with us

• Ongoing administration. We run your Build Place as a regular service, with the updates, builds and deployments on an agreed schedule.
• Cover for your own team. Support for in-house administrators: holiday cover, a second pair of hands at busy points, or an expert to call when a build will not go through.
• One-off clean-up. Taking over a Build Place left behind by an implementation project, getting it into a known, documented state, and handing it back or running it from there.

Why it matters

A neglected Build Place is the usual reason a routine service update turns into a project: modifications nobody can rebuild, deliveries that will not deploy, and environments too far apart to test properly. Keeping it in order is what makes the evergreen model affordable. If your solution also includes code modifications, see IFS customisation and modifications for how we build them to be easy to carry forward.

Frequently asked questions

What is the IFS Cloud Build Place?

It is where an organisation's own IFS Cloud solution is developed and built: the customer solution repository, the builds and the deliveries that are deployed to its environments through IFS Lifecycle Experience.

Do we need Build Place administration if we have few modifications?

You need much less of it. Configurations move between environments without code. Most organisations still have some code, in reports, integrations or modifications, and that has to be rebuilt with each update.

Can you take over a Build Place from our implementation partner?

Yes. We review what is there, get it into a known and documented state, and then either run it for you or hand it to your team.

Related services

• IFS consultancy from people who do the technical work
• IFS customisation and modifications that survive upgrades
• IFS Cloud service updates and release upgrades, done routinely
• IFS data migration, planned and reconciled
• IFS integration with the rest of your estate