Is it possible to build web version using eas-cli build command? I'm using eas.json file to manage different environment configurations, and I'm using iOS, Android & web versions, but for the moment I keep building the web using expo build, so the environments are always the same...
How can I manage the eas build for web?
Related
At present we're migrating our build infrastructure from expo with turtle to use EAS local builds. One of the issues we had with turtle is the need for setting up an external web host or use expo publish before you run turtle.
Does EAS local build still require the expo publish? step before calling the eas build --local?
First of all, I'm completely new in CI.
I am trying to set up a Jenkins to build several C++ projects I am hosting on my own Gitea instance.
The applications I want to add to my Jenkins build pipeline are mostly Qt or MSBuild projects.
I have installed the MSBuild plugin for Jenkins, however I couldn't find a Qt plugin.
Since the Jenkins docker container runs inside a Linux environment and runs on Linux itself too, I couldn't find out how to make Jenkins build MSBuild (.sln) or qt (.pro) projects.
How do I have to configure Jenkins to make it build MSBuild or Qt repositories?
Do I have to create makefile or CMakeLists files?
My goal is to have automated release builds inside my repositories built using my Jenkins docker container running on my Linux machine.
I really couldn't find a useful tutorial or explanation on this.
Thanks a lot in advance.
I am currently in the process of migrating a couple of legacy Qt5 projects to a new Team Foundation Server. All projects have been developed for Windows in Visual Studio using the Qt VS AddIn (and thus don't use .pro-files). I would love to use the TFS Build Agent to build these on other platforms (mainly linux).
I have previously done this on other projects using Jenkins and qmake, having platform-dependent settings in the .pro-file.
Is there an established workflow for building VS projects using Qt5 via a TFS Build Server on other platforms?
I don't use TFS but, since TFS Build operates on Visual Studio solutions, it ought to be possible to use the "Linux development with C++" feature of VS2017. Just setup a Linux project in the VS solution and it should build like any other.
Seems you'd like to build Cross-Platform Code in Linux using TFS vNext build system. To build or deploy you'll need at least one agent. The cross platform build agent is support on Ubuntu, Red Hat, and CentOS.
Detail steps please refer this tutorial-- Deploy an agent on Linux. Then simply create the build definition add build task, select the Linux build agent the same as build on windows. More detail step and build configuration you could take a look at this video tutorial-- Building and Deploy Applications In Linux With TFS
In your case, there is not corresponding VS/Qt VS AddIn in your Linux environment. You need to set up your Linux build agent local environment to build your qt5 application successfully, then it's not hard to build through tfs.
Another way is scripting the Linux build process to run over SSH or some other remote protocol, and driving this process from the Windows build agent.
I've developed a universal app for Windows 8.1 and am now trying to install the built .appx package via powershell having no problem after installing the certificate. Though when I run the installed app it behaves differently as if I deploy/install the app from within Visual Studio.
The app is using (local) REST services to obtain data from different sources. While working when starting the app from Visual Studio, it is not when I create an .appx package and install it manually via powershell. Any hints where the problem is located?
I have a windows 2012 server stack on cloud foundry.
I am trying to push a Java application(.war package) to this stack using Diego plugin.
The logs says that server started properly , but when i hit the application URL, I get a 404 error.
The same package works perfectly fine on linux stack.
Any help appreciated
At the present time, Windows support is for running Windows apps.
1.) ASP .NET MVC (12-factor ASP.NET MVC apps compiled against .NET 3.5+ were tested most extensively)
2.) Windows-compiled executables
3.) Batch scripts (with a manually specified start command)
https://github.com/cloudfoundry-incubator/diego-windows-msi/blob/master/docs/RELEASE-NOTES.md#supported-applications---known-to-work
Build packs will continue to run apps on Linux.