I've moved my fastlane folder out of the xcode directory, so I'm trying to get it to target it. I have this is my Fastfile:
increment_build_number(
xcodeproj: "../ember-cordova/cordova/platforms/ios/Patontheback.xcodeproj",
build_number: ENV['CIRCLE_BUILD_NUM']
)
Which gives
[06:50:47]: ------------------------------------
[06:50:47]: --- Step: increment_build_number ---
[06:50:47]: ------------------------------------
[06:50:47]: Error setting value '../ember-cordova/cordova/platforms/ios/Patontheback.xcodeproj' for option 'xcodeproj'
[06:50:47]: You passed invalid parameters to 'increment_build_number'.
[06:50:47]: Check out the error below and available options by running `fastlane action increment_build_number`
[06:50:47]: Variable Dump:
[06:50:47]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios beta", :SIGH_PROFILE_TYPE=>"app-store"}
[06:50:47]: Could not find Xcode project
xcodeproj definitely exists in that location:
$ ls -l ../ember-cordova/cordova/platforms/ios/Patontheback.xcodeproj
total 28
-rwxr-xr-x 1 kitsunde staff 25639 Sep 23 02:57 project.pbxproj
What am I doing wrong?
It's because it appends ../ to the path. So it's relative the parent directory and not the directory of the Fastlane file.
Related
Environment:
Jib version: 0.22
Build tool: Gradle
OS: Linux
Description of the issue:
We are adding a large sub-directory as a layer (~234MB)
Jib seems to build this layer locally even though it is cached locally and this operation takes around 25 seconds.
2022-09-29 00:28:25,133 sn:] - Jib Builder Log [DEBUG]: Building layer built sha256:a5ca6eb638e9710574d074247f77b640c0b1d86942c5e0fb1deaf3452325a7cb
This process takes about 25 seconds, then it says that layer already exists
2022-09-29 00:28:25,456 sn:] - Jib Builder Log [INFO]: Skipping push; BLOB already exists on target registry : digest: sha256:a5ca6eb638e9710574d074247f77b640c0b1d86942c5e0fb1deaf3452325a7cb, size: 234630578
bash-4.2$ find /tmp/jib_image_cache/ -name a5ca6eb638e9710574d074247f77b640c0b1d86942c5e0fb1deaf3452325a7cb -exec ls -lrt {} \;
total 229132
-rw-r----- 1 tomcat tomcat 234630578 Sep 29 00:28 7161988df87ff3006f5803117549fb6d14109073edfcde7b2d0d549dc706ad94
bash-4.2$ find /tmp/jib_image_cache/ -name a5ca6eb638e9710574d074247f77b640c0b1d86942c5e0fb1deaf3452325a7cb -exec ls -lrtd {} \;
drwx------ 3 tomcat tomcat 90 Sep 29 06:56 /tmp/jib_image_cache/layers/a5ca6eb638e9710574d074247f77b640c0b1d86942c5e0fb1deaf3452325a7cb
Expected behavior:
Is there any way to speed up the process?
There are 680 files in 38 sub directories under main directory.
Is it a good idea to add each sub directory or file as a layer?
We had some 12 agents (vsts-agent-linux-x64-2.188.4) running on one Az VM (Ubuntu 20.04.2 LTS) as processes (./config.sh && screen ./run.sh). All was well..
I had to run some command related to /tmp folder but it kept showing busy and we suspected that our Agents might be using /tmp. Unfortunately instead of any other clean way of stopping the agents, we killed all processes on this VM manually, including the agents'.
After the /tmp related command ran successfully, I tried running screen ./run.sh from one of the agent directories. And I got an error:
Failed to create CoreCLR, HRESULT: 0x80004005
I also had tried :
.agent2/run.sh and I got the error :
ldd: ./bin/libcoreclr.so: No such file or directory
ldd: ./bin/System.Security.Cryptography.Native.OpenSsl.so: No such file or directory
ldd: ./bin/System.IO.Compression.Native.so: No such file or directory
ldd: ./bin/System.Net.Http.Native.so: No such file or directory
Failed to create CoreCLR, HRESULT: 0x80004005
I even downloaded a new .tar for the agent and ran a fresh ./config . But I get the same error on ./config as well
Is there a solution to this? Please help
export COMPlus_EnableDiagnostics = 0, and then running ./config from the agent directory. worked!
I had this issue when running as the non-privileged user specified in the systemd file but running as root user worked fine.
Finally used:
strace -f -o trace.log /<executable path>/<executable name>
Which led me to:
9183 mknod("/tmp/clr-debug-pipe-9183-8112345738-in", S_IFIFO|0700) = -1 EACCES (Permission denied)
This caused me to compare the /tmp directory between working and non-working boxes.
[<not-working-hostname>]$ ll /
drwxrwxr-x 7 root root 93 Jan 5 21:37 tmp
[<working-hostname>]$ ll /
drwxrwxrwt 7 root root 93 Jan 5 21:59 tmp
(Note the r-x vs rwt)
Fix:
[<hostname>]# chmod 1777 /tmp
I have a self written recipe for nodejs because I need a specific Version. In the recipe I generate a symlink from /lib64 to /lib. When the symlink doesn't exist I got an error when I try to run node on my device.
do_install () {
# Create a symbolic link for the lib64 lib path
install -d ${D}/lib
ln -s /lib ${D}/lib64
}
FILES_${PN} += "/lib64"
I see in the build-history that the link exists but when I build the image I always get the following failure.
| /home/rail/yocto/build/tmp/work/odobox_e3900-poky-linux/odobox-developer-image/1.0-r0/recipe-sysroot-native/usr/sbin/prelink: Could not record directory /lib/modules-load.d: No such file or directory
| WARNING: exit code 1 from a shell command.
| DEBUG: Python function do_image finished
| ERROR: Function failed: prelink_image (log file is located at /home/rail/yocto/build/tmp/work/odobox_e3900-poky-linux/odobox-developer-image/1.0-r0/temp/log.do_image.3534)
Is there another solution for the problem?!
best regards Harald
Yocto introduced new linking tool "lnr"
I created a recipe example (lnr-example) on a sumo build environment:
LICENSE = "CLOSED"
SRC_URI = "file://lnr.bin"
FILES_${PN} += "/lib64"
FILES_${PN} += "/lib"
S = "${WORKDIR}"
do_install() {
install -d ${D}/lib/
install ${S}/lnr.bin ${D}/lib
lnr ${D}/lib/ ${D}/lib64
}
After building the example, here is the final "image" folder:
$ ls -l tmp/work/aarch64-poky-linux/lnr-example/1.0-r0/image
drwxr-xr-x 2 talel talel 4.0K مارس 30 10:44 lib/
lrwxrwxrwx 1 talel talel 3 مارس 30 10:44 lib64 -> lib/
Remember you need to package /lib as well, because it will fail if it contains some content, the issue is that the parent task which is /lib is not packaged, here is the error:
File './lib64/lnr.bin' cannot be packaged into 'lnr-example' because
its parent directory structure does not exist. One of its parent
directories is a symlink whose target directory is not included in the
package.
And, adding (IMAGE_INSTALL_append = " lnr-example") done without problems.
I'm having problems with files created from within Eclipse running on Linux.
All files (as far as I know) only gets the owner read and write permissions. Build output is the same but with the execute permission added.
The "test" file is created in Eclipse by File > New, and the "test1" file is created in command line by "touch" by the same user in the same folder.
-rw-------. 1 user stdgroup 0 Mar 15 10:22 test
-rw-r--r--. 1 user stdgroup 0 Mar 15 10:23 test1
My umask is set to 0022, so the output from the "touched" file is correct.
I'm running Eclipse Oxygen.2 Release 4.7.2 on Linux RedHatEnterpriseServer 7.3.
Anyone knows if there is a setting in Eclipse that can cause this, or any other ideas as to why this happens?
I use putty to log in to a solaris server. while i was performing a copy operation I pressed left arrow key to edit the file name but it kept adding this character ^[[D desperate I pressed return key and the copy operation got complete
cp temp.jar temp.jar^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D
I was planning to rename is as temp.jar.test, I used 'ls' command to check what has happened and to my surprise two files came up with same name!
root[dev1]# ls -lt temp*
-rw-r--r-- 1 root other 488554 Apr 11 02:25 temp.jar
-rw-r--r-- 1 root other 488554 Apr 11 02:22 temp.jar
-rw-r--r-- 1 root other 488554 Apr 11 02:22 temp.jar.041114
-rw-r--r-- 1 root other 488487 Sep 30 2013 temp.jar.032514
and I used 'rm' command to delete, the original file got deleted but the file copied with ^[[D character is not getting deleted. And I'm getting a msg like 'eisvr.jar.: No such file or directory'
Help me delete the file. I tried issuing 'rm temp.jar^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D^[[D'. It resulted in more errors.
The simplest way would be to run this command:
rm -i temp.jar?????????*
and answer yes when prompted to remove the bogus one.